Hello dear list!
I am applying for this year's GSOC  and I would like to contribute by
bringing GitLab  in Fedora. For those that don't already know
GitLab, it is a Self hosted Git management software written on Ruby on
Rails, pretty much like github's interface (you can try a demo here ).
It is a ruby app with lots of dependencies and I think this is a great
opportunity to extend the list of packaged gems supported by Fedora. Let
alone the fact that with the momentum GitLab has gained (it is in the
top 50 most popular open source projects on github) it would be an asset
if Fedora had this packaged. Also, the core developer was more than
willing to help with the process .
I could use any help needed on packaging. I have already exchanged a
couple of mails with Vit Ondruch and he pointed me to a direction. In
fact I am in the middle of reading all the related stuff from the wiki.
So what are your thoughts? Any guidance, ideas or insights are very much
PS. There is also the thought of deploying GitLab to git repositories on
fedorahosted.org, but that's irrelevant to this list.
Attached below are a few scripts which I threw together to help us
package cloudforms and to continue improving the gem -> rpm and bundler
-> yum conversion process.
The first rhgc.rb  extends the Fedora Gemfile checker I previously
sent out to compare a local gemfile against a variety of other services
including koji, distgit, bodhi, and more. The services and urls which it
queries is fully configurable from the command line so that the user can
easily customize what they want to check and where (either in Fedora or
RHEL). This script can be easily adapted going forward to setup bots
and/or git hooks which will send emails / error out / or do whatever
else should dependencies not be satisfied.
The second yrc.rb  is my first attempt at gem binary dependency
analysis against the local RH-based platform. Essentially it hooks into
/ overrides the normal binary gem building process (mkmf) to look for
errors when resolving dependencies, attempting to use yum to determine
which packages satisfy them. Multiple packages may satisfy a dependency,
for example both mysql-devel and mariadb-devel come up as satifying the
mysql header deps, but this should allow packagers to quickly lookup
packages that need to be included as BuildRequires in the rpm spec. This
is just a start, there is more we can do on this front in terms of
dependency resolution, using pkg-config  and extending gem2rpm with
this functionality for example.
Hope these help,
Today, I have proposed Ruby on Rails 4.0 as a change proposal for Fedora 20:
Any opinions, suggestions, help offers?
I know it was not discussed here before, but since tomorrow is change
proposal deadline, it is better to propose and tear it down then not
propose at all.
A while ago I posted a note on the Devise forum asking if anyone was
going to build an RPM for Fedora but didn't get any responses at all -
no-one even viewed the post! What happens with Gems in this category?
Am I supposed to do anything? Add a request somewhere? Use the Gem
instead of an RPM while I wait for someone to do the work for creating
the RPM? Should I bite the bullet and see how to produce the RPM
GPO Box 3411
Sydney NSW 2001
There are some gems that in order to run their test suite, they require
some other gems that are not yet packaged. For example see here  the
orm_adapter, where I have commented what we are missing.
I have seen this behaviour and with some other rubygem packages on gitweb.
Is it ok to omit some BuildRequires and to what degree is that tolerable?
FAS : axilleas
GPG : 0xABF99BE5