<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021, 5:50 PM Ken Dreyer <<a href="mailto:kdreyer@redhat.com">kdreyer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jan 21, 2021 at 2:12 PM Josh Boyer <<a href="mailto:jwboyer@redhat.com" target="_blank" rel="noreferrer">jwboyer@redhat.com</a>> wrote:<br>
> I can explain this.<br>
><br>
> Internally, we have a single comps file that looks almost identical to<br>
> the CentOS one referenced except for the branding changes already<br>
> mentioned. It delineates packages between repos using<br>
> "variant="BaseOS" or variant="AppStream", etc. For groups that have<br>
> packages split across repos, you'll see both variant statements within<br>
> the group definition. When pungi runs, it will take the single comps<br>
> file and deconstruct it based on variant statements to produce<br>
> per-repository comps definitions. That way the comps groups don't<br>
> include packages that are not actually in that repository.<br>
><br>
<br>
Thanks Josh, this clears up a lot. I also found<br>
<a href="https://docs.pagure.org/pungi/comps.html" rel="noreferrer noreferrer" target="_blank">https://docs.pagure.org/pungi/comps.html</a> and that helps me understand<br>
further how this process works.<br>
<br>
It sounds like CentOS engineers copy and transform an internal RHEL<br>
comps XML for CentOS 8 and push it to Pagure. And then when we get to<br>
CentOS 9 Stream, release engineers will make comps changes happen in<br>
CentOS' git first?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Engineering in general, but yes. For those interested before Stream 9 is available, the eln comps file in the fedora-comps repo is tracking things as they are developing.</div><div dir="auto"><br></div><div dir="auto">josh</div></div>