On Fri, Oct 18, 2019 at 12:02:32PM -0500, Merlin Mathesius wrote:
> On Thu, Oct 10, 2019 at 9:32 AM Merlin Mathesius
> wrote:
>
> >
> >
> > On Wed, Oct 9, 2019 at 4:05 PM Kevin Fenzi wrote:
> >
> >> On Mon, Oct 07, 2019 at 01:16:47PM -0500, Merlin Mathesius wrote:
> >> > I was asked to draft a p
On Thu, Oct 10, 2019 at 9:32 AM Merlin Mathesius
wrote:
>
>
> On Wed, Oct 9, 2019 at 4:05 PM Kevin Fenzi wrote:
>
>> On Mon, Oct 07, 2019 at 01:16:47PM -0500, Merlin Mathesius wrote:
>> > I was asked to draft a plan stating what EPEL 8 should do regarding
>> > Software Collections. The draft I c
I say put them in the main EPEL 8, without modules.
They get built against the default RHEL8 ruby module.
When RHEL8 get's another ruby module, then we can create and EPEL8
rubygem module that works for that RHEL8 module.
But have all the rubygems in non-module EPEL8, be built against the
default
Do we have a plan for how we want to handle ruby gems in EPEL8? ruby
is a module in RHEL8 so it seems like we would want to do that it a
modular way, which also suggests the possibility of a group effort to
produce a "EPEL8 rubygems" module. Or just dump them into the main
repo, at least fo
