On Mon, Aug 08, 2011 at 12:05:36PM -0400, Mo Morsi wrote:
> 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.
>
I agree, it's a maintenance hassle, and should be discouraged except for
where strictly necessary. The Fedora Ruby community should try to
converge on a single Ruby stack wherever possible (honestly I think
we've been good with this so far).
I see that as the problem; i.e., there won't ever be a single stack that
everybody wants to (or can) use. We need some flexibility so that
someone can, for example, keep using Rails 2.3 on a later Fedora; i.e.,
there's no reason they should have to migrate to 3.0 just to get a newer
Fedora release.
--
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/