On 25.04.2017 13:54, Jan Engelhardt wrote:
On Tuesday 2017-04-25 13:40, Stephan Kulow wrote:
On 25.04.2017 13:29, Jan Engelhardt wrote:
Yesyes, you posted a solution to the %macro problems, but I am still keen on hearing your nondestructive solution for /etc/os-release's VERSION_ID, if there is any.
While I understand you insist on increasing version numbers, I don't really see too many technical arguments for it actually.
Because most real life cases I can think of won't be able to use a reliable > no matter how often openSUSE screws version numbers anyway. Because you just don't know any details about future versions.
It's not about future versions but past ones:
if (v < 1200) dit; else if (v < 1300) dat; else if (v < 4200) dot; else { current practice, hope that it will work for enough future versions until the next script revision is out }
Should they have written ">= x00 && <= xx99" instead? Maybe. Either way, they could have not know that 1500 would come along.
Right - but such as life in the dungeon called open source. Many upstreams have funny ideas as well - not just about version numbers. But as Richard said, telling the world now that openSUSE is crazy and that the release next year will be completely off the version scheme should give enough time for people adopting to 42.3 to consider 15 as they write their conditions and receipes. Greetings, Stephan -- FLASH! Intelligence of mankind decreasing. Details at ... uh, when the little hand is on the .... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org