theforeman
Fixes #36579 - Split the installer into multiple subpackages
This creates separate RPMs for each scenario. This allows the user to install just a single scenario and never use the --scenario parameter.
Packages created:
- foreman-installer-scenario-$scenario foreman/katello/foreman-proxy-content scenarios
- foreman-installer-common Puppet modules, Hiera data and other shared files
- foreman-installer Transitional package that requires foreman-installer-scenario-foreman for a smooth migration
Split off from https://github.com/theforeman/foreman-packaging/pull/8814 and requires https://github.com/theforeman/foreman-installer/pull/870
Before I do the same to Debian packages I'd like some agreement on that this is a good structure.
You asked for Debian… I think there the situation is a tad easier. Given we have no Katello/FPC there, and there is no standalone-proxy scenario today, we can rather safely split things up into foreman-installer-common and foreman-installer-scenario-foreman (as here), make foreman-installer an empty, transitional package only pulling in f-i-s-foreman. Then, a few releases later, we can force the removal of the transitional package (using Breaks/Replaces) and drop it completely.
