From: Evan Phoenix <evan@...>
Date: 2010-04-16T03:03:04+09:00
Subject: [ruby-core:29536] Re: [Bug #3140] gem activation has changed  between 1.8 and 1.9


On Apr 15, 2010, at 2:57 AM, Ryan Davis wrote:

> 
> On Apr 14, 2010, at 20:36 , Rich Kilmer wrote:
> 
>> 1) Make RubyGems packaged files accessible with require/load in 1.9
>> without having to require 'rubygems'
>> 2) Minimize startup time (don't load the full rubygems library if its
>> not going to be used)
>> 3) Load rubygems proper if need be.
> 
> Is 1 a real requirement tho? I'm not sure it is. If it isn't, moving gem_prelude to something like 'rubygems/fast' would allow users a clean and easy choice of: a) nothing at all, leave me alone; b) rubygems proper; c) rubygems via the gem_prelude strategy.

I think that goal 1 can't be achieved without loading the normal rubygems logic because of the very bug we're working on here.

To load a gem properly, you need to know it's dependencies so you can load the proper versions. RubyGems isn't setup for being able to load those dependencies outside itself easily.

So while I think this is an admirable goal, it's simply too hard to reach without reorganizing RubyGems itself significantly.

> 
> You can even no-op rubygems/fast if defined? Gem, so it can be overridden via the commandline in case of a special conflict.
>