Hello, on Montag, 19. September 2011, Vincent Untz wrote:
Le dimanche 18 septembre 2011, à 20:07 +0200, Jan Engelhardt a écrit :
obsoletes/provides relation: Obsoletes: foo < %version Provides: foo = %version
Sascha mentioned this case in his talk about packaging best practices.
The recommendation is the following:
- if there's a version update at the same time, use < - if there's no version update, use <=, and add a comment specifying for which version this was done, so people know when it's safe to go to <.
So far, so good, but: does it really make sense to use %version for the obsoletes? IMHO a hardcoded version would make more sense... For example, let's assume foo was renamed to bar, and the latest version of foo was 1.5. In the meantime, there is bar 5.0 - and a new project foo 2.0 that does something totally different than foo 1.5 or bar 5.0. With the above sniplet, foo would always be replaced by bar. What about: Obsoletes: foo <= 1.5 Provides: foo = %version This should still replace all old bar packages up to 1.5, but avoid the problem that foo 2.0 will be replaced even if it is something totally different. Opinions? Regards, Christian Boltz -- Geld. Wie profan. Mein Rechner braucht eine Champagnerkühlung beim downloaden. Glucker. Mich kühlt Astra. [Ratti in fontlinge-devel] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org