On Fri, Oct 29, 2010 at 1:47 AM, Mohammed Morsi <mmorsi(a)redhat.com> wrote:
So here is an idea I just came up with. gem and rpm are both package
formats, so we have gem2rpm to perform the conversion from the dev
community format to the Fedora system format. If rvm and yum are both
package manement systems, and the dev community perfers rvm while Fedora
prefers yum, would a tool such as rvm2yum make sense? This wouldn't
solve the problem of having one standard Ruby/Fedora deployment scenario
which I still think would be necessary, but if we combine it with
something like Copr, we could also support deploying custom ruby
software stacks for various purposes, all integrated with Fedora.
https://fedoraproject.org/wiki/Category:Copr
Supporting custom stacks while having a standard/official stack is a nice
idea. And depending on how it's done it could be a better solid approach.
With the above suggestions and polisher, I think it could certainly have a
good appeal.
I'd love Fedora to be the foremost Ruby dev/deploy platform and the
same time I belong also to the crowd who wants Fedora boxes to be
managed with Puppet (or Chef, etc.). So while I would want to deploy
multiple stacks, I'd certainly want to have a standard stack in Fedora.
Haven't spent time considering all the ramifications, and as
suggested
we would still need to come up with an 'official' stack to ship with
Fedora itself. Any thoughts?
Great discussion. Which also reminds us of the state
of Ruby in distros.
I was a little ambiguous in my last mails regarding couple of things. I too,
do agree that we should have an official stack. My suggestions is that we
look towards 1.9.x for F15.
MRI development is concentrated on 1.9.x and people seems to be
gradually moving from 1.8.x towards that, and most of the popular
projects support 1.9.x already.
-Mo
--
Gaveen Prabhasara