|
A SIG for people who are interested in improving the state of Ruby in Fedora. This includes packaging Ruby libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Ruby packages for Fedora.
State of Affairs
We are always happy to get more Ruby packages into Fedora. That means that you, dear reader, can become a hero by packaging your favorite piece of Ruby code as an RPM and submitting it to Fedora.
- We are closely following Ruby MRI development. Once a new Ruby release gets in the wild it is packaged for Rawhide.
- All Ruby implementations should be able to use gem provided by the single package, but we are not yet there.
Creating RPM's
The guidelines for building Ruby packages can be found on a separate page.
Oliver Andrich has created a specfile template for Ruby packages that is included in rpmdevtools 1.5 and later. Please start with this template when packaging Ruby code for Fedora.
Gems and RPM
Ruby has its own packaging format, gem, meant to be a cross-platform way to distribute Ruby software. Gems carry much of the metadata that RPM's carry, but not all of it, and because of their cross-platform nature violate the LSB. Gems that contain shared libraries also do not play nicely with multilib.
Please use the 
rubygem-gem2rpm
Bundler and RPM
Fedora doesn't allow vendorizing packages without special exception, but this does not mean bundler based applications cannot be used with the Fedora stack.
The bundler_ext gem loads the system-installed versions of packages specified in a Ruby application Gemfile, providing a simple mechanism to switch between custom ruby stacks and distro-supported stacks.
The polisher gem implements many downstream / post-publishing operations and querying mechanisms. Developers and end users can utilize these to check the state of their Ruby gems and applications and move them along custom workflows.
Useful tools
- gem2rpm Generate an rpm from a rubygem.
- pkgwat Checking that your project's gems are available in Fedora/EPEL repos.
- gem-compare A RubyGems plugin that compares versions of the given gem.
- polisher A Ruby module and set of utilities aimed to assist the post-publishing packaging process for Ruby gems and applications.
- bundler_ext Simple library leveraging the Bundler Gemfile DSL to load gems already on the system and managed by the systems package manager (like DNF/YUM/apt).
References
Ruby
Ruby-Doc.org
RubyGems.org
fedora-ruby repository at GitHub
Mailing list
ruby-sig mailing list
IRC Channel
#fedora-ruby[?] on freenode.net
Web portal
Currently Open Ruby Package Review Bugs
The Ruby SIG also likes to get more Ruby packages into Fedora. This is the list of opened review requests for ruby packages.
Meetings
There are not too many chances to meet and discuss Ruby topics related to Fedora. But you can always hold an IRC meeting.
Join the Ruby SIG
We are always glad for new contributors. If you are interested in joining the SIG there are a few steps to do first:
Join the mailing list
To join the mailing list, you must subscribe to ruby-sig mailing list. Important news, discussions, and announcements take place there.
Send a self-introduction
Send a self-introduction mail to Ruby SIG mailing list to introduce and tell us a bit about yourself. Tell us why are you interested in contributing and what area do you want to contribute to. Also you can share with us what projects are you working on and your role there. Additionally, it is the perfect place to ask what do you need help with to get started, maybe something left you confused? Just ask.
Join #fedora-ruby channel on IRC
Next step would be joining the #fedora-ruby[?] channel on the FreeNode IRC network.
Create an FAS Account
To be able to contribute to Fedora you will need a FAS account and sign the Fedora Project Contributor Agreement if you have not already.
Members
Members of Ruby SIG are tracked by ruby-sig FAS group. The minimal requirement to get sponsored to the group is to went through all the steps above. Members of the group are awarded this nice small badge.
The old list of members, prior we used ruby-sig FAS group, can be found in wiki history