[CentOS-devel] Extras in CentOS Stream 9

Mon Nov 8 05:52:30 UTC 2021
YATIN KAREL <yatinkarel at gmail.com>

On Thu, Nov 4, 2021 at 2:50 AM Brian Stinson <bstinson at redhat.com> 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?
>
> --Brian
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel at centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>

+1 This would be great for SIGs !!

Thanks and Regards
Yatin Karel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20211108/b88c925e/attachment-0002.html>