RPMs are a must, but the question is where do we generate them? If we stand up our own
rubygems server, we could have that server generate RPMS and then grab them from there
whenever we do a bundle install or gem install. Or the other option of generating an rpm
locally could also work.
=========
Tyler Smart
Check out the IT.rb group:
https://docspace.corp.redhat.com/groups/itrb
----- Original Message -----
From: "Lukas Zapletal" <lzap+fed(a)redhat.com>
To: ruby-sig(a)lists.fedoraproject.org
Sent: Friday, August 5, 2011 10:12:25 AM
Subject: Re: Distributing Rails 3 apps
On 08/05/2011 02:11 PM, Tyler Smart wrote:
Number 2 does sound the best, but I have had an idea that I think
would be an interesting project. It involves standing up a Fedora RubyGem server and
forking bundler so that we can tie it into yum. Whenever you install a gem package, gem
actually calls yum and grabs the gem-rpms from our server. We could have gem2rpm spit out
a src rpm that we can feed to brew (for the gems that require compilation) and all others
are just noarch. That way we can still develop in "the ruby way" but do it all
with RPMS. This idea still needs fleshing out, mind you, but I think it is worth looking
at.
Interesting idea, but as Vita said later in the thread - RPMs are a must.
Thanks for tips!
--
Later,
Lukas "lzap" Zapletal
_______________________________________________
ruby-sig mailing list
ruby-sig(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig