Bringing GitLab in Fedora
by Axilleas Pipinellis
Hello dear list!
I am applying for this year's GSOC [0] and I would like to contribute by
bringing GitLab [1][2] 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 [3]).
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 [4].
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
appreciated!
Regards,
Axilleas
PS. There is also the thought of deploying GitLab to git repositories on
fedorahosted.org, but that's irrelevant to this list.
[0] https://fedoraproject.org/wiki/GSOC_2013
[1] http://gitlab.org
[2] https://github.com/gitlabhq/gitlabhq
[3] http://demo.gitlabhq.com/
[4] https://groups.google.com/forum/?fromgroups=#!topic/gitlabhq/SQMDi-yyXmU
10 years
packaging automation scripts
by Mo Morsi
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 [1] 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 [2] 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 [3] and extending gem2rpm with
this functionality for example.
Hope these help,
-Mo
[1] https://gist.github.com/movitto/6086381
[2] https://gist.github.com/movitto/6086386
[3] https://github.com/ruby-gnome2/pkg-config
10 years, 2 months
About bootstrap-sass and bundled javascript
by Achilleas Pipinellis
Hi,
I have submitted a review request of bootstrap-sass [0] and after a
discussion with Troy, we kinda agreed to ship only what is included
in vendor/assets/stylesheets and leave out the javascripts folder.
Whereas this might seem like a solution by the standards of Fedora
guidelines [1], I am curious whether this package will work after all.
(Please take a moment to read our discussion. I thought that it would
be better to further discuss it here for future reference.)
If we don't ship the javascript folder, then a rails developer wouldn't
have to also install Twitter bootstrap separately for this to work?
There is also a gem named twitter-bootstrap-rails [2] that does the same
job but ships the native less css. So, I get it that a rails app can
have either one of these gems, right?
If that's the case, I think we must ship the javascripts of each gem,
even if this seems like bundling.
On a side note, I have been following the packaging ML and the
discussion about the guideline drafts on web assets and javascript [3].
In that case, it would make sense to split the javascripts and place
them in `_assetdir` as stated by [4]. I think bootstrap-sass case falls
in second bullet.
tl;dr;
gems that use bundled javascript code should ship it until guidelines[3]
become official.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=982679
[1]
https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system...
[2] https://github.com/seyhunak/twitter-bootstrap-rails
[3]
https://lists.fedoraproject.org/pipermail/packaging/2013-July/009304.html
[4]
https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/JavaScript#In...
--
FAS : axilleas
GPG : 0xABF99BE5
Blog: http://axilleas.me
10 years, 2 months
Policy re Gems that don't have RPMs yet?
by Philip Rhoades
People,
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
myself?
Regards,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
10 years, 2 months