146 karma · joined November 12, 2021
https://github.com/AlmaLinux/ALESCo/pulls?q=is%3Apr+is%3Aclo...
https://repo.almalinux.org/almalinux/10/isos/x86_64_v2/
We even do a full EPEL rebuild for it as well.
Edit: also, it's literally the true version of the story. Do your own research. It's all public and logged.
If you read the mailing list archives you'll see the truth.
I think you're reading into the changes completely wrong. AlmaLinux has power to actually do things, fix issues, contribute real and meaningful changes, all while maintaining 100% compatibility. A lot has been done already, with plenty more to come, with 0 compatibility issues.
Let us know if you have any issues!
Basically the goal is still to fit the exact situation you just brought up. I'm not aware of this ever not being the case if it weren't to be the case for some reason, then we have a problem we need to fix.
All of the extra stuff we do, patch, etc. is with exactly what you just stated in mind.
Underneath it all, compatibility is what matters. At AlmaLinux we still target RHEL minor versions and will continue to do so. We're a clone in the sense of full compatibility but a derivative in the sense that we can do some extra things now. This is far, far better for users and also let's us actually contribute upstream and have more of a mutually beneficial relationship with RH versus just taking.
Formerly we were just 100% downstream RHEL with none of this nuance, as you mentioned.
Oracle has no influence over AlmaLinux.
CloudLinux is a large financial sponsor of AlmaLinux still, and probably always will be. The rest of what you said couldn't be farther from the truth.