different behavior for RPM dependency handling between yum andapt

[Matthias Saou]

Konstantin Riabitsev wrote :

> I *am* on the yum design team, and this subject has been mulled over 
> a whole lot back when the problem of gated reinstalling zebra 
> reinstalling gated came out. The result of the deliberations was that:
> 
> a) obsoletes are unlikely to happen within a lifetime of a release, 
> so yum should do "update" and ignore obsoletes.
> b) when going to a subsequent release, one should use "yum upgrade" 
> so obsoletes can be resolved and applied.

And I'd like to add :
before a or b) using obsoletes omitting a version should be considered a
packaging but.

Say that you want "foo" which is currently up to 1.0 to be replaced by
"bar" 0.1, you should put into bar-0.1 a "Obsoletes: foo <= 1.0" line in
order to later be able to introduce "foo" back in some day, and either then
have it be compatible (ability to install both) or have it in turn obsolete
"bar" up to a certain version.
But hey, it's just like epoch... once you've done it wrong without knowing,
it's stuck forever.

Hmmm, drifting a bit from the initial topic, sorry.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Raw Hide 20030710 running Linux kernel 2.4.20-20.1.2013.nptl
Load : 0.03 0.08 0.03