[EPEL-devel] Re: Documentation for EPEL modules?

2020-05-18 Thread Petr Pisar 
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  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  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


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Documentation for EPEL modules?

2020-05-16 Thread Antonio Trande 
On 15/05/20 14:57, Stephen Gallagher wrote:
> On Fri, May 15, 2020 at 7:57 AM Petr Pisar  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  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?

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x7B30EE04E576AA84
GPG key server: https://keys.openpgp.org/



signature.asc
Description: OpenPGP digital signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Documentation for EPEL modules?

2020-05-15 Thread Petr Pisar 
On Fri, May 15, 2020 at 06:30:04AM -0500, Richard Shaw wrote:
> On Fri, May 15, 2020 at 6:15 AM Petr Pisar  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.

-- Petr


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Documentation for EPEL modules?

2020-05-15 Thread Petr Pisar 
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.

In Fedora, a name of a module must match the name of the repository, and
a name of a stream must match the name of the branch.

(Technically, it's possible to diverge, but Fedora's infrastructure enforces
it.)

If what you want is "cmake3:latest" module stream, then you need:

$ fedpkg request-repo --namespace modules cmake3
$ fedpkg request-branch --namespace modules --repo cmake3 latest

Also please note that modules undergo a review. So for a new module, you need
an approved review first and the "--exception" argument should not be used.

-- Petr


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[EPEL-devel] Re: Documentation for EPEL modules?

2020-05-15 Thread Antonio Trande 
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

2) Writing a `modulemd` file based on this example [1]:

[1]
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/

3) Build the module:

$ fedpkg module-build


On 14/05/20 17:51, Petr Pisar wrote:
> On Thu, May 14, 2020 at 06:46:29AM -0500, Richard Shaw wrote:
>> So this happened:
>>
>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ad02b27ee3
>> https://bugzilla.redhat.com/show_bug.cgi?id=1830748
>>
>> TLDR; So we need an updated version of CMake in EPEL 8 but RHEL/CentOS
>> already provide a "3" version. Worse both the Fedora and EL versions
>> provide "cmake3" packages and binaries so it's not possible to install the
>> cmake3 package in EL 8.
>>
>> So here's a great use case for modularity but I have no idea how it works
>> and there doesn't seem to be any EPEL specific documentation even though
>> it's obviously getting used:
>>
>> https://bodhi.fedoraproject.org/releases/EPEL-8M
>>
>> Do we need a epel8 branch? Or is the EL module created from master?
>>
> I believe modules in EPEL are similar to modules in Fedora. I'm not aware
> about a documentation for modules in EPEL. There were some attempts to draft
> the guide lines like forbiding default streams and mandating stream prefixes,
> but I do not remember any output.
> 
> Let's look at real examples.
>  lists 
> avocado-latest-820200512173744.9edba152 module. That's this
>  module build
> in Koji. The Source field reads 
> .
> 
> Theat means "fedpkg clone modules/avocado" and there these branches:
> 
> * latest
>   remotes/origin/52lts
>   remotes/origin/69lts
>   remotes/origin/HEAD -> origin/latest
>   remotes/origin/f29
>   remotes/origin/latest
>   remotes/origin/master
>   remotes/origin/stable
> 
> The module stream is called "latest", let us check "latest" branch:
> 
> commit 12e2140e759fdb0a4477ab2432c411a4452d8efc (HEAD -> latest, 
> origin/latest, origin/HEAD)
> Author: Merlin Mathesius 
> Date:   Tue May 12 12:37:44 2020 -0500
> 
> Rebuild with avocado 79.0.
> 
> Signed-off-by: Merlin Mathesius 
> 
> So you can see the module is built from a non-epel8 branch. An avocado.yaml
> file lists these dependencies:
> 
>   dependencies:
>   - buildrequires:
>   platform: []
> requires:
>   platform: []
> 
> So "platform" is left empty to expand it by MBS on all available platforms. If
> you look at koji listing
> , there are
> five modules avocado-latest-*20200512173744 builds of from the same sources.
> That probably means that Koji attempts to build the module for all Fedoras and
> EPEL 8. Technically, it's possible to override the platform with "fedpkg
> module-build" command, but I cannot see any trace of it in the logs.
> 
> That buld was performed by "merlinm" users. You can ask him for more details.
> 
> -- Petr
> 
> 
> ___
> devel mailing list -- de...@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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/de...@lists.fedoraproject.org
> 

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x7B30EE04E576AA84
GPG key server: https://keys.openpgp.org/



signature.asc
Description: OpenPGP digital signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org