Le Mardi 22 Juillet 2003 01:55, Andi Payn a �crit : > It does seem a bit conceptually weird to me when a package obsoletes itself > (wouldn't it make more sense to "Obsolete: foo < %version"?), but since > there's no harm done, I decided it was better not to focus only on the > handful of packages where there was an actual problem in practice.
I forgot this point: to be exact, but it's very hard to do: If foo died at version 1.0, and was renamed to bar, spec should be: Name: bar Version: %version Release: %release Obsolete: foo <= 1.0 Provides: foo > 1.0 but you don't allways know when the project was renamed, and skipping version is soo simple ! I don't think I will try to find latest version of package foo, assuming rpm don't take care when the package obsolete itself ! -- Linux pour Mac !? Enfin le moyen de transformer une pomme en v�ritable ordinateur. - JL. Olivier Thauvin - http://nanardon.homelinux.org/
