Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: The future of OpenSUSE Leap

  1. #11
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    5,127

    Default Re: The future of OpenSUSE Leap

    Quote Originally Posted by microlinux View Post
    folks who argue against stable releases,
    Yes, but, the Elephant in the room of stable releases of every Linux distribution is, currently, some dependency issues with Python and Ruby versions …
    • And, the simple fact that, the Ruby version being used by system components of stable releases is End-Of-Life …
    • And, some conflicts between the Python version used by Kernel/System components and, the Python version required by some newer applications …

    The Server world is possibly more affected than the Desktop world because, some large customers have Python scripts performing major tasks which are not compatible with newer Python versions …

    We'll have to make a decision as to what's more important –
    • Systems doing useful work and generating revenue or,
    • Newer applications which assume that, the newest version of the scripting language is always installed and available …

  2. #12
    Join Date
    Sep 2010
    Location
    Poland
    Posts
    1,974

    Default Re: The future of OpenSUSE Leap

    Interesting discussion. It seems like a difficult problem to tackle. I'm preety sure openSUSE folks will make a reasonable decision so I'm not too worried
    Best regards,
    Greg

  3. #13

    Default Re: The future of OpenSUSE Leap

    Definitely an interesting discussion and I see a lot of this around the internet. I don't work for SUSE and I haven't been a user for that long, so take what I say with a grain of salt.

    I find it hard to believe that SUSE would be killing Leap off for multiple reasons.

    1.) They literally just finished fully integrating Leap with SLE in 15.3
    2.) One of the points of that was to make "upgrading" from Leap to SLE easier I think
    3.) Packagehub - this is a big boost for SLE in many ways and is basically the Leap Backports repo if I understand correctly. It's entirely maintained by openSUSE and would be bad for SLE if this integration was removed
    4.) I'm sure there are other reasons that I don't know about

    Yes, Leap is going to be different in some ways. But I just can't see it getting killed off. And knowing what I know about openSUSE, the upgrade from 15.5 to 16 is going to be a breeze like all the others. Not only am I not worried in the slightest bit, I'm excited about the changes. It sounds great to me!

  4. #14
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    16,124
    Blog Entries
    3

    Default Re: The future of OpenSUSE Leap

    Quote Originally Posted by rootetsy View Post
    Yes, Leap is going to be different in some ways. But I just can't see it getting killed off. And knowing what I know about openSUSE, the upgrade from 15.5 to 16 is going to be a breeze like all the others.
    Yes, I share that view. Let's not give into a premature panic.
    openSUSE Leap 15.4; KDE Plasma 5.24.4;
    testing Tumbleweed.

  5. #15
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    5,127

    Default Re: The future of OpenSUSE Leap

    Quote Originally Posted by nrickert View Post
    Let's not give into a premature panic.
    The current working view mentioned during the openSUSE Conference Q&A with the ALP team, was a time to initial release of about 2 years …

  6. #16
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,692
    Blog Entries
    15

    Default Re: The future of OpenSUSE Leap

    Quote Originally Posted by dcurtisfra View Post
    The current working view mentioned during the openSUSE Conference Q&A with the ALP team, was a time to initial release of about 2 years …
    Jumps into the time machine......

    Miniatures attachées Miniatures attachées Click image for larger version. 

Name:	Screenshot from 2022-06-22 09-52-47.png 
Views:	431 
Size:	101.7 KB 
ID:	1094  
    Cheers Malcolm °¿° (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #17

    Default Re: The future of OpenSUSE Leap

    Weird thread ... I'm not sure I even totally understand it ....


    But just a few thoughts as to the future of leap ... hope it helps.

    Leap is currently an extended (read: desktop / average user ) version of SLES. RHEL (Redhat Enterprise Edition Linux) and SLES (Suse Linux Enterprise Sever) have largely replaced the big OS names of yesterday (SunOS, Solaris, Irix, AIX, HPUX, ..., ... , ... ). GNU/Linux is what runs the internet! GNU/Linux is at the heart of many big corporate and research IT infrastructures (as well as some still very cool quasi legacy IBM Mainframe stuff, that run "linux" personalities and such). In addition to being ROCK stable, Leap is just a really great OS ... I don't think you can wrong with it.

    Flatpak (and I do generally hate flatpak) provides a robust means to support legacy apps. A stupid personal example: I use a flatpak to provide "displaycal", which is essential software to me, but is no longer supported, or even installable as it is based on python2.

    In the world of *nix/open/gnu ... there are many ways to skin a cat as things change.

    Reality today:


    Code:
    charles@orca$ cat "food in tins"
    cat: 'food in tins': No such file or directory
    As I remember fondly, the same from SunOS once upon a time:
    Code:
    charles@orca$ cat "food in tins"
    cat: can not open "food in tins"

  8. #18
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    5,127

    Talking Re: The future of OpenSUSE Leap

    Quote Originally Posted by microlinux View Post
    Explaining distribution release cycles and the concept of low-risk security updates and backports to my students is part of my job, you know.
    Some more information about Transactional Systems and Containerised Systems – <https://yast.opensuse.org/blog/2022-...-report-2022-9>.

    And, digging deeper into Transactional Systems and Containers, it seems that, the idea is, to allow those applications which need newer libraries than the default libraries supplied with the base system, to run in a Container which, contains the needed library versions.
    • Sounds like Flatpak but, it ain't –
    • It seems that, you'll be able to point YaST – or the successor to YaST – to a Container and, associate all the applications with versions which need the newer libraries to that Container.

    In other words, a new abstraction layer within the system …

    Sounds almost like “Bye, bye, library version mismatch woes” – which isn't a bad idea IMHO but, I suspect that, we'll have to wait and see …

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •