Investment reinforces SUSE’s commitment to innovate and support SUSE Linux Enterprise distributions and related open source projects
SUSE plans to contribute its code to an open source foundation
So what will SUSE’s plan be for the SUSE fork to maintain compatibility going forward - won’t they have the same problems accessing RHEL source code as Rocky and Alma to maintain compatibility?
The source code will still be available, the GPL2 still applies. As far as I understand, RedHat will publish the upstream code that will eventually end up in RHEL. This article can explain it better than I can: https://www.theregister.com/2023/06/23/red_hat_centos_move/
The article says that upstream code in CentOS Stream has brief periods where it is in sync with RHEL around major releases. So rebuild distorts can access RHEL compatible code at those times.
What I don’t understand though, is how do the RHEL-derived distros stay in sync with “bug for bug” (or close as possible too) compatibility with RHEL proper between those release windows? That sounds like it would only be possible with access to sources for RHEL patches and updates. Which is now legally complicated to access RHEL source code. Taking patch code from CentOS Stream would likely differ enough from what actually makes it into RHEL to break the “bug for bug” level of compatibility. Unless there is some way accurately derive what goes into RHEL from CentOS Stream that I’m not understanding.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@lemmy.world
This is a most excellent place for technology news and articles.
So what will SUSE’s plan be for the SUSE fork to maintain compatibility going forward - won’t they have the same problems accessing RHEL source code as Rocky and Alma to maintain compatibility?
The source code will still be available, the GPL2 still applies. As far as I understand, RedHat will publish the upstream code that will eventually end up in RHEL. This article can explain it better than I can: https://www.theregister.com/2023/06/23/red_hat_centos_move/
The article says that upstream code in CentOS Stream has brief periods where it is in sync with RHEL around major releases. So rebuild distorts can access RHEL compatible code at those times.
What I don’t understand though, is how do the RHEL-derived distros stay in sync with “bug for bug” (or close as possible too) compatibility with RHEL proper between those release windows? That sounds like it would only be possible with access to sources for RHEL patches and updates. Which is now legally complicated to access RHEL source code. Taking patch code from CentOS Stream would likely differ enough from what actually makes it into RHEL to break the “bug for bug” level of compatibility. Unless there is some way accurately derive what goes into RHEL from CentOS Stream that I’m not understanding.