Support #21855
Updated by Peter Amstutz about 1 month ago
Because CentOS has mutated from being a stable RHEL-compatible distro to a rolling distro that is no longer a suitable development target, we will stop supporting it in Arvados 3.0. That makes it weird to have the repository path https://rpm.arvados.org/CentOS This should be renamed https://rpm.arvados.org/RHEL and the relevant package build scripts and documentation updated to use that. (I spent an inordinate amount of time trying to figure out if there was a naming scheme we should be following but came up empty, so RHEL is the most straightforward name to use here.) For backwards compatibility, https://rpm.arvados.org/CentOS should continue to exist and serve already-released packages. For simplicity we could link CentOS and RHEL to the same directory, but that will eventually lead to weird things like packages showing up in a "/CentOS/9" directory when CentOS 9 doesn't exist. Also, should we be distributing against point releases? E.g. perhaps our packages should be "/RHEL/8.6" because we are using python 3.9 packages that were not in the 8.0 release but became available in a point release later. (I don't know what the best practice is here, it seems that the client is configured with just the /RHEL/ path and selects the appropriate version on its own). For example, https://download.rockylinux.org/pub/rocky/ lists has individual point releases. It looks like releases, although it may be that the point releases are point-in-time, and the major release version simply tracks the most recent point minor version. So for our own packaging, where our packages are going to be the same for all supported point releases within a major version, there's probably no reason to break it out by separate RHEL point releases.