Bug#80573: should replace grafix
On 00-12-27 Peter Palfrader wrote:
> On Wed, 27 Dec 2000, Christian Kurz wrote:
> > > grafix-dev should conflict with grafix, (at least this is what
> > > I think currently :-).
> > No, I think those files that are in both package, should only be in one
> > package. I think the -dev package would be the appropriate one.
> grafix is the old package,
> it was replaced by grafix1 and grafix-dev.
> grafix1 and grafix-dev can live nearby quite happily.
> grafix1 shares a set of files with grafix.
That's fine as grafix is an old package.
> So does grafix-dev.
But that is not fine. No package should contain any files that are in an
other package already. So the correct solution is to put those
conflicting files either in grafix1 or grafix-dev.
> > > But I have another question I hope people on -qa can answer:
> > > How is upgrading supposed to work?
> > > Let's say I have grafix installed and run an apt-get dist-upgrade.
> > > IMHO it should upgrade grafix to grafix1, but I could not get it
> > > to work with several mixes of Conflicts, Replaces and Provides.
> > You need to have a "Replace: grafix" and a "Conflicts: grafix".
> > "Provides" is useful for virtual package but not for upgrading.
> So apt-get dist-upgrade will not catch it and wait until you
> manually install grafix1 or grafix-dev?
I never used dist-upgrade, so I can't comment on this.
Ein "Nein" ausgesprochen mit der tiefsten Überzeugung ist besser
und größer als ein "Ja" um zu gefallen oder noch schlimmer, um
Schwierigkeiten zu umgehen.
-- Mahatma Gandhi