[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-25 Thread Petr Pisar
On Tue, Sep 24, 2019 at 09:13:51PM -0400, Stephen Gallagher wrote: > > Example: RHEL has two perl streams: > > > > perl:5.24 > > perl:5.26 [d] > > > > You can add a non-modular perl-Foo package into EPEL bacause EPEL magically > > adds perl:5.26 into the build root. > > > > If you add a perl-Foo

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-25 Thread Petr Pisar
On Tue, Sep 24, 2019 at 05:02:42PM -0600, Orion Poplawski wrote: > On 8/26/19 2:33 AM, Petr Pisar wrote: > > On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: > > > So, I see the following options for how to handle default streams in RHEL > > > 8 > > > > > > Option 1: We

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-24 Thread Petr Pisar
On Tue, Sep 24, 2019 at 08:44:56PM -0400, Stephen Gallagher wrote: > On Fri, Aug 23, 2019 at 5:49 PM Kevin Fenzi wrote: > > > > On 8/23/19 10:56 AM, Stephen Gallagher wrote: > > ... > > > > For default profiles, we have some options as well: > > > > > > Option 1: We disallow setting default

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-24 Thread Stephen Gallagher
On Fri, Aug 23, 2019 at 1:56 PM Stephen Gallagher wrote: > > As you know, we delayed support of Modularity in EPEL (called > Application Streams in RHEL) until 8.1 while we worked out some > remaining issues. Some of those issues were technical, but we have a > few others that will come down to

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-24 Thread Stephen Gallagher
On Mon, Aug 26, 2019 at 4:33 AM Petr Pisar wrote: > > On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: > > So, I see the following options for how to handle default streams in RHEL 8 > > > > Option 1: We disallow assigning default streams at all within EPEL 8. > > This will

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-24 Thread Stephen Gallagher
On Fri, Aug 23, 2019 at 5:49 PM Kevin Fenzi wrote: > > On 8/23/19 10:56 AM, Stephen Gallagher wrote: ... > > For default profiles, we have some options as well: > > > > Option 1: We disallow setting default profiles for EPEL streams. Pros: > > no risk of conflict with RHEL, should they now or

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-09-24 Thread Orion Poplawski
On 8/26/19 2:33 AM, Petr Pisar wrote: On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: So, I see the following options for how to handle default streams in RHEL 8 Option 1: We disallow assigning default streams at all within EPEL 8. This will protect us against a future

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-08-27 Thread Pat Riehecky
On 8/26/19 3:33 AM, Petr Pisar wrote: On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: So, I see the following options for how to handle default streams in RHEL 8 Option 1: We disallow assigning default streams at all within EPEL 8. This will protect us against a future

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-08-26 Thread Petr Pisar
On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: > So, I see the following options for how to handle default streams in RHEL 8 > > Option 1: We disallow assigning default streams at all within EPEL 8. > This will protect us against a future change where RHEL wants to set a >

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-08-23 Thread Kevin Fenzi
On 8/23/19 10:56 AM, Stephen Gallagher wrote: > As you know, we delayed support of Modularity in EPEL (called > Application Streams in RHEL) until 8.1 while we worked out some > remaining issues. Some of those issues were technical, but we have a > few others that will come down to policy. In