Richard Kilmer wrote:
> 
> On Dec 26, 2007, at 11:55 PM, Eric Hodel wrote:
> 
>> On Dec 26, 2007, at 13:44 PM, Gonzalo Garramuñï wrote:
>>
>>> For ruby, I also turned off RUBYOPT=-rubygems, which is perhaps a tad 
>>> incorrect now, as rubygems is now part of 1.9.   That also raises the 
>>> question whether rubygems *can* be turned off in 1.9 as you could in 
>>> 1.8.
>>
>> RubyGems is not loaded in 1.9 until you use it (some method on Gem).  
>> See gem_prelude.rb for details.
> 
> All the highest version gem's paths are pushed on $: in gem_prelude.rb 
> every time Ruby starts.  This was to remove the need for the 
> require/load hack in Ruby 1.8.  gem_prelude creates a stub module for 
> Gem.  I you access any constant or method on Gem (beyond a gem method 
> that resolves into an already available path) it will load rubygems.rb.  
> If you want to disable this altogether:
> 
> ruby --disable-gems <options> whatever.rb
> 

Posting to a new thread, as I just found out some weird behavior....


-- 
Gonzalo Garramuñï
ggarra / advancedsl.com.ar

AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy