Re: Announcing EPEL-8.0 Release

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 22 Aug 2019 at 03:54, Paul Howarth <paul@xxxxxxxxxxxx> wrote:
>
> Hi,
>
> On Wed, 14 Aug 2019 10:50:24 -0400
> Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
> > ## Known Issues:
> > 1. EPEL-8.0 does not come with modules. Packages built for perl,
> > python and other modules are only built against “default” modules. For
> > example installing a perl library from EPEL will work with the
> > perl-5.26 but not with the perl-5.24 module.
>
> Will this present a problem going forward when modules are available in
> EPEL-8 and it's possible to build for both perl-5.24 and perl-5.26?
>

No it is not currently possible. perl-5.24 is not a default so
anything depending on 5.24 needs to be also a module.

> i.e. will the presence of non-modular perl packages built against 5.26
> cause any issues for people wanting to use the perl-5.24 module?
>

Those should all get uninstalled if you switch to perl-5.24

> Maybe if the perl modules become buildable at a point release, all the
> perl packages could be removed from the main EPEL-8 repo at that time
> and moved into modules?
>

That will be up to a maintainer doing so. EPEL as I have been reminded
constantly in the last year is a community and not a product. If the
maintainers have no interest in modules.. then modules aren't going to
happen. If the maintainers do, then modules will happen. If the
maintainers can't agree on making modules happen or not.. we will end
up with a repeat of the Fedora java problems. In the end, it will be
people problems versus technology problems.


> Apologies if this is a stupid question but modularity is still
> something of an unknown to me.
>

You and me both :).

> Paul.
> _______________________________________________
> 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



-- 
Stephen J Smoogen.
_______________________________________________
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




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux