On Sat, May 16, 2020 at 11:43:00AM +0200, Antonio Trande wrote: > On 15/05/20 14:57, Stephen Gallagher wrote: > > On Fri, May 15, 2020 at 7:57 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote: > >> > >> On Fri, May 15, 2020 at 06:30:04AM -0500, Richard Shaw wrote: > >>> On Fri, May 15, 2020 at 6:15 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote: > >>> > >>>> On Fri, May 15, 2020 at 12:42:15PM +0200, Antonio Trande wrote: > >>>>> Shortly (Martin is in Cc to confirm): > >>>>> > >>>>> 1) Make a module: > >>>>> > >>>>> $ fedpkg clone cmake3 > >>>>> $ fedpkg request-repo --namespace modules --exception cmake3-latest > >>>>> $ fedpkg request-branch --namespace modules --repo cmake3-latest epel8 > >>>>> > >>>> This will request for creating "cmake3-latest" module and "cmake3-latest" > >>>> repository and "epel8" stream and "epel8" branch. I don't know if you > >>>> really > >>>> want to create "cmake3-latest:epel8" module stream. > >>>> > >>> > >>> Since this is a module, is there any point in using the cmake3 namespace > >>> over just cmake? > >>> > >> I cannot see any point. Maybe if there were cmake-2 or cmake-4 incompatible to > >> cmake-3 but installable in parallel, then it would make sense. (Like Python.) > >> Because you cannot install more streams of the same module at the same time. > >> Otherwise I would also go with plain "cmake" module name. > > > > > > It turns out, cmake already has a presence[1] in the modules namespace > > of dist-git. It is a relic of the Modularity 1.0 effort, but it's > > already there and that will make this easier. > > Petr, can you take care of this module for epel8, too? > I cannot because of a lack of time and interest in CMake. But I can transfer an ownership of the module to whoever wants it. Also please note that at that time CMake bundled various libraries and a second build-only cmake-bootstrap module was needed to build the cmake module properly. I will include it into the gift. -- 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
