![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 7/6/22 22:03, Dan Čermák wrote:
"jdd@dodin.org"
writes: Le 06/07/2022 à 13:44, Predrag Ivanović a écrit :
Just to be clear, I am in the same boat. My desktop is 2core/8gb RAM, so no oS ALP for me :)
oh... ok, so ALP is not to be a Leap replacement anytime soon?
ALP is a completely new code stream and *not* the next SLE. Whether the community will build an "openSUSE-ALP" is for us to discuss and decide.
I think this is a bit of an unfair characterization, from the perspective of the community no SLE-16 has ever been mentioned and there has been plenty of talk of not doing Leap from SLE-15-SP6 and on which really leaves the community with only one choice which is building Leap from ALP sources. Now presuming that SUSE still uses rpm's as a basis for building most of its containers it would probably be possible with some amount of effort to create a distro thats more like the current Leap by making sure the rpm's have the appropriate conflicts then putting them all into one repo so it functions more like a traditional linux distro. But frankly claiming the community has any choice about whether the community does or doesn't use ALP as the basis for the next Leap is simply unfair unreasonable and unacceptable unless something else is announced or comes along. So from that perspective the community should be doing everything it can and pushing for everything it can to ensure that it is possible to create a Leap replacement out of the pieces of ALP that its given. At the end of the day its up to SUSE to decide on what the community gets but its still in SUSE's best interest when something isn't hard to do to make life easier for the community to do it. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B