Hello, As we have started the effort to have all components, bundled in the SF image, packaged we are figuring out that EPEL and RDO repo are helpful as a bunch of dependencies are available there. Unfortunately on a SF installation if yum is freely usable then an operator can break its SF deployment if EPEL or RDO lands something that break an ABI.
Usually it should not happen with EPEL as explain in the upgrade policy: https://fedoraproject.org/wiki/EPEL_Updates_Policy https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies RDO have stable releases that should not introduce ABI breakages over the time. Relying on both EPEL and RDO can increase the risk so it may be better to only rely on one of them and RDO includes stuff we care about like olso, openstack clients ... (+ a lot of pkg from EPEL) so better to only rely on RDO IMO. Also there's the solution of only relying on base centos managing the deps by ourself but the work seems quite huge for a small team ... ? Also after discussing with Nico it can be safer to only enable centos-update and sf RPM repos and disable the rest at the end of the built of the image to avoid eventual unexpected pkg bumps from RDO or even EPEL according to our choice. Cheers, Fabien _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
