On Thu, 16 May 2019 at 09:59, Chris Adams <linux@cmadams.net> wrote:
So, I don't have a handle on the whole modularity thing... still trying
to understand what's what with that.  But this caught my eye in your
"Open Questions":

- Some normally leaf packages like screen are inside of the Red Hat
  hidden buildroot package set. Having them built in EPEL is likely to
  cause conflicts on user systems and divergence with RHEL. EPEL
  maintains agreed upon policies for these cases so using the repo
  doesn’t cause pain for RHEL customers or users.

What does that actually mean?  I'm a consumer of CentOS rather than RHEL
these days, so I haven't really dug into version 8 yet.  I do use screen
a lot, so what does "inside of the Red Hat hidden buildroot package set"
mean for me?


RHEL-8 was built with various packages which are not shipped in BaseOS/AppStream/CRB. Some like screen are in the buildroot for the packages which depend on them but were decided not to be shipped. Thus they are hidden buildroot set. They were however branched to CentOS git repository. While building a newer version of screen and putting it in EPEL might not break anything, other packages might cause problems which we don't have the resources to track down and debug. So I would like to not have EPEL rebuild any package which was branched to CentOS EL-8. 

I will clarify the document.

 
--
Chris Adams <linux@cmadams.net>
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org


--
Stephen J Smoogen.