On Fri, May 15, 2020 at 08:58:21AM -0000, Alexander Korsunsky wrote: > Hi there, > > the version of CMake that is currently packaged with RHEL/CentOS 8 is 3.11, > which is becoming more and more outdated. Me (and a few other people, > judging by bug report participation) would quite like to have a newer > version of CMake on their systems. > > Now, if I understand correctly, according to the EPEL policies, > https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy, it is > prohibited to replace packages from the base distribution. It is, however, > allowed to replace these packages in modules that are not enabled by > default. > > Unfortunately, nobody really seems to know how to build modules for EPEL. > There is documentation for Fedora: > https://docs.fedoraproject.org/en-US/modularity/making-modules/ . However, > being not very familiar with modularity, I have no clue which parts of the > documentation apply to EPEL, and I could not find EPEL-specific > documentations and recommendations. I have seen some threads on this list > *discussing* these, but it's hard for me to discern the consensus and best > practices from mailing list threads. > > Would the Modularity magicians be so kind as to reply with some pointers on > how to create modules for EPEL? If that already exists, my apologies, I hope > you can direct me to that resource. > I replied to the same question yesterday on Fedora devel list <https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/FULNP2XFGCV5MT5U6VYLQZITDTSBEG7U/#2AOC6F2VMAD563ABD6AOV7JPPJGX7L3C>. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
