3 ms·
They haven't put anything behind a wall. You want CentOS Stream and RHEL source code? Then go get it! Here it is! [1] [1]: https://git.centos.org/ https://git.
by davisr 3y ago
They haven't put anything behind a wall. You want CentOS Stream and RHEL source code? Then go get it! Here it is! [1]
[1]: https://git.centos.org/ https://git.centos.org/
When you buy RHEL, you even get the entire source code on a DVD for the exact binary distribution that you download.
- grosswait 3y agohttps://www.redhat.com/en/blog/furthering-evolution-centos-stream https://www.redhat.com/en/blog/furthering-evolution-centos-s...
- creatonez 3y agoThe repository you linked previously contained RHEL source code, but it is no longer being updated as of a few weeks ago. This is the entire thing being discussed. Really weird for you to be grandstanding about how misinformation is bad, while spreading it yourself.
- davisr 3y agoSorry, here you go [1]. Last activity 28 minutes ago. [1]: https://gitlab.com/redhat/centos-stream https://gitlab.com/redhat/centos-stream Additional docs: https://docs.centos.org/en-US/stream-contrib/techinfo/buildsystem/#_gitlab https://docs.centos.org/en-US/stream-contrib/techinfo/builds...
- creatonez 3y agoClose, but this is not RHEL source code.
- davisr 3y agoYes, it is now. From Red Hat's original June 21 article [1] (they even put it in bold). > CentOS Stream will now be the sole repository for public RHEL-related source code releases. RHEL is in there somewhere, even if a user has to pick specific commits for it. Furthermore, for the totally-bundled source for the exact binary RHEL release (which Red Hat only is required by the GPL to give to their customers, whom they already gave a binary to): > For Red Hat customers and partners, source code will remain available via the Red Hat Customer Portal. [1]: https://www.redhat.com/en/blog/furthering-evolution-centos-stream https://www.redhat.com/en/blog/furthering-evolution-centos-s...
- creatonez 3y ago> RHEL is in there somewhere, even if a user has to pick specific commits for it. This is not true. There are Red Hat package versions that do not correspond to any commits in that repository. For example, if a package gets updated from 1.1.0 to 1.2.0 in CentOS Stream, then later a patch is released (lets say, 1.1.1, or 1.1.0-2) then that patch will never show up in this repository. In such a situation, the 1.2 version will probably get an equivalent patch eventually, but not the 1.1 version. Others have pointed out that embargoed security patches are not pushed to CentOS Stream until the embargo ends, and often at the end of the embargo they still don't push it until several weeks later, due to RH developers forgetting to do so.