Hello, Am Dienstag, 31. Mai 2016, 08:23:23 CEST schrieb Christoph Grüninger:
thanks for your feedback. I don't get why this should be better. I did not change this part. I only see the disadvantage of your suggestion, that next time this place is overlooked to change.
Actually this is exactly the point ;-) - the Obsoletes never needs to be changed to a higher version number.
By the way, the last version packaged for openSuse was SuperLU 4.3
This means you'll never need to obsolete a superlu package newer than 4.3. Obsoletes: superlu < 4.4 is a close match, which will obsolete only packages that really existed. Obsoletes: superlu < %{version} will also obsolute packages with a (from today's POV) future version number that probably will never exist - but if they do [1], it will become interesting[tm] to install such a package. Yes, I know / hope this rarely happens in practise - but why make things harder than they need to be? Regards, Christian Boltz [1] possible reasons include: - in some years superlu 7.0 could come with a new tool that should be packaged in a package named "superlu". - someone starts a totally different project which is for some reason also named "superlu" (maybe he/she just didn't google if that name is already used by something else). With the < 4.4, he/she will "just" need to fast-forward the version number once, but with < %{version} the version must always be higher than the version of superlu-devel - or the package needs to be renamed. --
Einmal im Jahr sorgen MS Produkte durch das Internet für Milliardenschäden in der Wirtschaft 2000: Love Letter, 2001: Code Red und Nimda, 2003: Sapphire, 2002? Windows XP. [Eric Wick, Wolfgang Ewert und Urs Traenkner in dcsm]
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org