Rocky Linux claims that there are other ways to get RHEL sources
twitter.comAnd they've just posted the article about how they plan to get the sources without violating the RH ToS:
> Another method that we will leverage is pay-per-use public cloud instances. With this, anyone can spin up RHEL images in the cloud and thus obtain the source code for all packages and errata
How does this approach not require them to agree to the ToS/EULA mentioned earlier in the post?
they themselves never created an account in red hat site, that would require then to accept either the ToS or the EULA..
They spined up an VM in some service that started an red hat image with the required license already in place for that image..
it is the vm provider that is bound by the EULA, not RockyLinux..
They are bound by the ToS for the VM provider they are using, that does not prevent them to get the sources from Red Hat..
At what point do we just move on...?
Seems pretty clear IBM is hostile to anyone using RHEL source to repackage an OS from, so anyone using a RHEL derivative is putting themself at risk.
Time to start using Debian.
unfortunately a lot of software used by companies is RHEL only..
If you need the software and does not want to pay red hat the derivatives are the only option..
Or fork and potentially let it diverge.
In the replies they link to this blog post with the details.
Using the UBI images and public cloud instances does seem like a clever way to handle that.
I started giggling when I read the part about using cloud instances.
here's hoping that red hat don't modify dnf to require some kind of key to get source code from the default repo, as stupid as that would be.
it already does.. you need an valid license to use DNF.. you can even get the RHEL install ISO but you will not get updates unless you active a license..
but some cloud providers offer vm with the license already in place, they pay the license in embed the cost in the vm price.. so the cloud provider that is bound by the eula..