On Dec 2, 2006, at 15:43 , Steve Ross wrote:
> Devin Mullins wrote:
>> Steve Ross wrote:
>>> The odd thing is that any requires *inside a Rails app* seem to  
>>> find the
>>> gems just fine. I assume that's because Rails munges the load paths.
>> Actually it's because of config/boot.rb in your Rails app.  
>> Specifically:
>>      require 'rubygems'
>>
>> If your code was working before, and didn't need this, then it's
>> possible that you had had RUBYOPT set.
>>
>> Devin
>
> You're right, it's the explicit:
>
> require 'rubygems'
>
> Shouldn't this be implicit? Or am I misremembering...

You are misremembering.

Some people set RUBYOPT=-rubygems (or is it RUBY_OPT?)

-- 
Eric Hodel - drbrain / segment7.net - http://blog.segment7.net

I LIT YOUR GEM ON FIRE!