https://bugzilla.redhat.com/show_bug.cgi?id=1744676 Petr Pisar <ppisar@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ppisar@xxxxxxxxxx | |) | --- Comment #3 from Petr Pisar <ppisar@xxxxxxxxxx> --- The only information I have is <https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/HXFHAPXPG2FX4NHP2WDNE3J3JXE53LML/>. My interpretation is that it's not possible to build Modularity modules in EPEL 8. And there is yet another issue: There are a few Perl packages modularized in RHEL. I'm sure people will want EPEL to provide their modularized rebuilds, so that users can switch to a different perl and still enjoy all the other Perl packages. A straightforward implementation is copying sources from CentOS to EPEL, wrapping them with a module and building the module in EPEL 8 while letting a stream expansion to build it for all perls. The downside is that the modular package would mask RHEL package. That was forbidden in EPEL 7 and I believe the same rule will apply to EPEL 8. There are few ways how to deal with it but none of them is simple. We need to clarify it with EPEL project owner and choose a right strategy in Perl/EPEL sig. I'd like to elaborate about it more in some list. Do you prefer Fedora's perl-devel or EPEL's epel-devel? I'd rather use perl-devel for discussing the strategy. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ perl-devel mailing list -- perl-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to perl-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/perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
