Re: Bug#2807: X <-> cpp dependency?
David Engel writes ("Re: Bug#2807: X <-> cpp dependency?"):
> > David Engel (firstname.lastname@example.org) wrote on 25 April 1996 20:45:
> > >A better arrangement might be to make the gcc package a superset of
> > >the cpp package and have it provide and conflict with the cpp package.
> > Yes, but not conflict!!!!!! Provide and replace. I think there are a
> > lot of "conflicts" that should be replace-provide instead. Like
> > libc>=11 :-(
> No, the conflict needs to be there to make sure cpp would be removed,
> especially if replaces is also used. I mentioned a few weeks ago that
> I was concerned that the overloading of replaces could be problematic.
> In this case, using provides, conflicts and replaces is ambiguous as
> to whether cpp and gcc are two independent, alternative packages
> (which the would be) or gcc should obsolete cpp.
I'm somewhat confused. What precisely do you want to do ?
Are cpp and gcc independent alternative packages ? If so then you
should use Provides/Conflicts.
If cpp is obsolete then you should use Replaces/Conflicts and perhaps
What situation do you have ?