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 RHEL8 ruby module. Troy p.s. The rubygems that are currently in -playground, are from me, for KDE. I'm currently in the process of putting them in regular EPEL8. I'm letting the regular maintainer build them if they wish, or if they don't want (such as the ones Vic owns) I'm maintaining them for EPEL8. On Fri, Oct 18, 2019 at 7:19 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > > Hi Orion, > > I myself don't plan to build anything for EPEL8 with possibly > rubygem-gem2rpm exception. Also, I would suggest against modules. > > > Vít > > > > Dne 18. 10. 19 v 16:14 Orion Poplawski napsal(a): > > 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 for now. Or something else? > > > > > > We currently have some ruby packages in epel directly, and some just > > in playground: > > > > ruby-caca 0.99-0.43.beta19.el8 > > ruby-caca 0.99-0.43.beta19.epel8.playground > > rubygem-builder 3.2.3-6.el8 > > rubygem-hpricot 0.8.6-26.epel8.playground > > rubygem-introspection 0.0.4-6.el8 > > rubygem-metaclass 0.0.4-8.el8 > > rubygem-mustache 1.0.2-8.epel8.playground > > rubygem-qpid_proton 0.29.0-1.epel8.playground > > rubygem-rake-compiler 1.0.7-3.epel8.playground.1 > > rubygem-rdiscount 2.2.0.1-5.epel8.playground > > rubygem-ronn 0.7.3-13.epel8.playground > > > > ruby-caca gets built from libcaca - not sure how those kinds of > > libraries should be handled. > > > > Currently I'm holding off building shapelib (and thus plplot) for > > EPEL8 directly due to its dependency on rubygem-ronn (and its deps) > > until we sort this out. > > > > Thanks! > > _______________________________________________ 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
