this post was submitted on 11 Jul 2023
128 points (99.2% liked)
Technology
58104 readers
3729 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.