Hi,
Hello folks,
In the planning of next Community build services, a new question came up.
In the past we never allowed EPEL repositories to be used as external
repositories for SIGs. Doing so, would allow to build against EPEL
packages and not duplicate the work for maintainers in EPEL/SIGs.
However it would mean also building against a moving target which can be
difficult if EPEL policies are the same as today.
As EPEL 8 is also in the making it would be good to hear what SIGs think
about this specific issue.
In CloudSIG we currently are explicit about not supporting enabling EPEL
repos to deploy OpenStack. We are rebuilding the required deps in the
SIG repo when needed. The main reasons for this is that we want to stay
with specific versions of dependencies for stable releases and not
following latest builds in EPEL on every supported release. Also,
rebuilding them in CBS allows us to test any update before pushing it to
the actual repos.
Those are valid reasons for doing that. There is a side effect that people seem to want both and then our two groups are each blamed for breaking each other. But that is mostly people not reading the directions and aiming a loaded gun at their foot.
Do you use any other SIG work or is it a 'we rebuild everything we need and don't rely on others'? Also would it help you to rebuild or push back fixes if the source code you used for that was shared?
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel