On 04/25/2017 11:30 PM, Simon Lees wrote:
On 04/25/2017 10:44 PM, Rüdiger Meier wrote:
On 04/25/2017 03:05 PM, Greg Freemyer wrote:
On Tue, Apr 25, 2017 at 8:53 AM, Stefan Seyfried email@example.com wrote:
On 25.04.2017 14:26, Christian Boltz wrote:
So even without the 42.x -> 15.x leap (pun intended), it seems version numbers are already confusing ;-) I know switching to 15.x adds slightly more confusion now, but on the long term it's much better to have SLE, Leap and suse_version in sync than always having to do the "+ 30" math for the Leap version.
As I already mentioned, we could just go for 150, 151, 152, 160...
This would still be tied to SLES in an obvious way, and not backwards from 42.x
Best of both worlds.
At a minimum that should be done in /etc/issue.
And maybe %leap_version 1500000, 1510000, 1520000, 1600000, ... in rpm macros.
I still don't get why do we need to be tied to SLES version numbers at all. What is the technical reason behind this? It is pure unimportant cosmetics.
Well the two distro's share a significant number of source packages that are the same so being able to refer to them in the same way in places makes a reasonable amount of sense.
The following shows us that around 1890 of the 9296 packages in Leap 42.2 come directly from the SLE equivalent, most of these packages are core parts of the distro, think systemd, dbus, gtk, qt etc. So from a technical perspective being able to version them the same certainly has advantages.
simon@tek-top ~ ➤ osc -A https://api.opensuse.org cat openSUSE:Leap:42.2:Update 00Meta lookup.yml | wc -l 9296 simon@tek-top ~ ➤ osc -A https://api.opensuse.org cat openSUSE:Leap:42.2:Update 00Meta lookup.yml | grep "SLE-12" | wc -l 1890