On Fri, Aug 23, 2019 at 5:27 AM Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > The following answers are just my opinions and not policy. > > On Fri, 23 Aug 2019 at 06:52, Petr Pisar <ppisar@xxxxxxxxxx> wrote: > > > > Case: RHEL delivers an M module with no default stream, there is no S stream. > > Can I add a new S stream into EPEL and make it default? I'm not sure this will > > be allowed. There is a risk of creating conflicts between streams transitively > > required by another default streams. (Remember the libgit2 module conflict > > <https://bugzilla.redhat.com/show_bug.cgi?id=1717117>.) > > > > I would be against that. However I am not sure how we would police > that.. [because there is no one to do that kind of work.] > I'm not against making an EPEL module/ stream for a module already in RHEL8. I am *very* against making it a default. Even if the module in RHEL8 doesn't have a default. You will be changing the RHEL8 experience for *all* EPEL8 users, even if they have no interest in your module. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
