71
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Jul 2023
71 points (100.0% liked)
Linux
4395 readers
267 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 1 year ago
MODERATORS
How can SUSE maintain RHEL compatibility when source-code for future versions are no longer going to be publicly available?
Rocky Linux have said that they can rebuild using publicly available sources in UBI containers and cloud images.
https://rockylinux.org/news/keeping-open-source-open/
Though reading the article, I don't know if SUSE is simply rebuilding or forking. In any case, it's cool to see SUSE committed to open source principles.
SUSE doesn't HAVE to do that. That's kind of a grey area. It's legal, but kind of skirting things.
What you can do is get RHEL, take a look at all the packages and their changelogs, git history, find the code in CentOS, and then build your own from scratch. It's a ton more work, Rocky wouldn't have the resources to do it, but SUSE will.
Just realized, can't do git history, because they wouldn't package in the git files as that'd be internal to RHEL.
Thank you. The SuSE blogpost uses the word “fork”
The source code IS publicly available in CentOS Stream gitlab repos. The thing that isn't public anymore is the pre-packaged SRPM snapshots of that code. This effectively means that if clone makers want to keep cloning RHEL, they have to pull from CentOS Stream and do some Engineering work instead of throw a script at a pile of SRPMS to rebuild them. This whole thing has been weirdly blown out of proportion in my opinion.
Disclaimer: I work for Red Hat so feel free the grain of salt my statements and flame me if you feel so inclined. I don't mind people being upset about the change, I just want people to be mad at the right thing if they are going to be mad.