Bringing GitLab in Fedora

[Vít Ondruch]

There are some of them already undergoing review:

awesome_print - https://bugzilla.redhat.com/show_bug.cgi?id=839650
backports - https://bugzilla.redhat.com/show_bug.cgi?id=816991 - though 
I am not sure if we should continue with this one, since it brings 
nothing new to Fedora
bootstrap-sass - https://bugzilla.redhat.com/show_bug.cgi?id=920436
faraday - https://bugzilla.redhat.com/show_bug.cgi?id=820063
rails_best_practices - https://bugzilla.redhat.com/show_bug.cgi?id=839649
ruby-progressbar - There is rubygem-progressbar, which seems to be the 
same library: https://bugzilla.redhat.com/show_bug.cgi?id=642666 there 
was also rubygem-ruby-progressbar review: 
https://bugzilla.redhat.com/show_bug.cgi?id=737551 - Although this one 
was deferred, not sure if we should not name the gem by upstream
spork - https://bugzilla.redhat.com/show_bug.cgi?id=588476 - This was 
deferred
stringex - https://bugzilla.redhat.com/show_bug.cgi?id=728051
yajl-ruby - https://bugzilla.redhat.com/show_bug.cgi?id=823351 - This is 
blocked by upstream a bit :/

And there are some which are in Fedora already:

facter - https://admin.fedoraproject.org/pkgdb/acls/name/facter

And also others, which are not yet in Fedora, but they are packaged by 
their upstream, such as Foreman. The Katello Koji instance [1] might be 
good source for packages like that. Katello guys are eager to get their 
dependencies into Fedora as far as I know.

Some of them should not be needed at all:
libv8 - This is used by therubyracer as far as I know. The system libv8 
is used for therubyracer instead and if there is other need, it should 
be used there as well.
rb-fsevent - This is Mac specific gem. It is useless on Linux. And that 
is exactly the thing which is problematic for collaboration with Ruby 
community :/ It is very probably dependency of Spork, so it should not 
be needed anyway. In the worst case, Spork can use polling by default.


And also, please note that you are listing also the development 
dependencies, such as Spork. Spork is no way needed for run-time nor 
build-time. It is pure development tool, which allows you to run your 
test suite as soon as you save some changes. We should eliminate such 
gems from the list. Not that we don't want them in Fedora, but just 
because they are out of scope for this project IMO.

Vít



[1] http://koji.katello.org/koji/packages



Dne 11.4.2013 11:36, Dan Allen napsal(a):
>
> Absolutely fantastic write-up. This is exactly the type of update that 
> starts the effort off on the right foot and gets the community behind 
> it. Thank you for posting.
>
> I just went through the process of packaging a few gems, so *if* I 
> have time, I'd be happy to grab a few from the list and get them 
> packaged or do reviews.
>
> Best of luck!
>
> -Dan
>
> --
> Sent from my CyanogenMod-powered
> Android device, an open platform for
> carriers, developers and consumers.
>
> On Apr 10, 2013 11:59 AM, "Axilleas Pipinellis" <axilleas at archlinux.gr 
> <mailto:axilleas at archlinux.gr>> wrote:
>
>     Hello everyone! It's been over a month since I last wrote to this list
>     regarding the GitLab project.
>     I managed to make a blog post of the story so far[0], any feedback
>     welcomed :)
>
>     Cheers!
>
>
>     [0] http://axilleas.github.io/en/blog/2013/bringing-gitlab-in-fedora/
>     _______________________________________________
>     ruby-sig mailing list
>     ruby-sig at lists.fedoraproject.org
>     <mailto:ruby-sig at lists.fedoraproject.org>
>     https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
>
>
>
> _______________________________________________
> ruby-sig mailing list
> ruby-sig at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/ruby-sig/attachments/20130411/b2d94abd/attachment-0001.html>