How do we want to handle ruby gems in EPEL8?

[Orion Poplawski <orion@xxxxxxxx>]

  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!

--
Orion Poplawski
Manager of NWRA Technical Systems          720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion@xxxxxxxx
Boulder, CO 80301                 https://www.nwra.com/

Attachment: smime.p7s
Description: S/MIME Cryptographic 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