On 03/11/2021 22.20, Brian Stinson wrote: > Hi Folks, > > With CentOS Stream 9 we are publishing SIG content separately from OS > content to make things easier to deliver > (http://mirror.stream.centos.org/9-stream/ vs. > http://mirror.stream.centos.org/SIGs/). Everything under the 9-stream > directory corresponds to a repository in RHEL and repo files are > included by default in centos-stream-repos at install time. > > Currently (in CentOS Linux) SIGs build their own repo files into > centos-release-<sig> packages and ask for their release in CentOS > Extras. We also ship things like epel-release and elrepo-release in > Extras. I'd like to continue this in Stream 9 but make things a little > bit easier for SIGs to self-manage their repo packages. > > Proposal: > - Extras will continue but as a SIG repository, including the > appropriate tags in CBS, and a separate gpg key > - Extras, beginning with Stream 9, will not contain any other content > besides repo packages > - Extras will be the only SIG repo included in centos-stream repos (to > allow folks to dnf install other repo packages) > - Each SIG leader (or a designate) will be an ex-officio member of the > group, allowed to tag centos-release-<sig> packages in for publishing > - Other repositories (like EPEL) may also have a member designated to > manage its release package > > If this is something SIG leaders are interested in, I will take a > formal proposal to the board for sponsorship. Any comments? > +1 Sounds good to me. Just one thought: Having in mind the possible availability of RHEL buildroots in CBS [1]. Can this same method be used for SIG content built for RHEL 9? I don't see anything that speaks against it, but I'm probably missing something. It would actually only require users to add the extras repo (for RHEL 9) and then they can simply install further repo packages. [1]: https://pagure.io/centos-infra/issue/400