SCL handling in packaging and installer

Hello everyone,

Currently there’s a package foreman-release-scl which ensures the right repositories are set up. Historically we’ve depended on centos-release-scl which contains SCLs by CentOS. However, nowadays we only depend on centos-release-scl-rh (which we copy into our repositories). This package sets up repositories for the CentOS rebuilds of Red Hat SCLs and creates a weird situation for RHEL users who have supported SCL packages.

My proposal is to drop foreman-release-scl and centos-release-scl-rh altogether from our repositories and require users to set these up themselves. We’ll update the manual to instruct the user. The upgrade instructions should tell the user to verify this.

The installer will lose all its abilities to manage the repository. This is not a loss because since 2.0 these repositories actually need to be set up prior to running the installation (which prompted this RFC).

On a more technical level foreman-release should bsolete foreman-release-scl so it’s removed from the users’ system. The centos-release-scl-rh should remain.