On Mon, Aug 08, 2011 at 11:41:28AM -0400, Mo Morsi wrote:
>> Is there any way to evolve RPM to handle this sort of
scenario?
>
> Chris Lalancette and I have been talking about exactly this issue. I'm
> not 100% sure it's appropriate for Fedora, but I don't think there's
> any getting around Fedora users' needs to install parallel stacks of
> application code (RVM, as mind-bogglingly evil as it is, exists to
> serve a need -- if we could fill that need in a less evil way we would
> be doing the Ruby world a service, I believe).
>
> --Hugh
Well bundler is supposed to be a way to manage parallel stacks of gems
on a per-application basis. We just need to make sure that the
Gemfile.lock that ships in our project releases match the rpms being
shipped in Fedora.
In any case, parallel stacks should be straightforward, as they are
already exist in Fedora, whether it be via 'compat' packages or putting
the version from the name-version-release into the name (such as with
python1.9)
The downside to that is that every new release of a gem will require 1)
a new package and 2) a new package review since the name is now directly
coupled to the version of the gem.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/