[Rubygems-developers] Can't require 'rubygems/specification' anymore?

Luis Lavena luislavena at gmail.com
Tue Dec 8 11:40:00 EST 2009


On Tue, Dec 8, 2009 at 1:33 PM, Trans <transfire at gmail.com> wrote:
>
>
> On Dec 8, 10:19 am, Luis Lavena <luislav... at gmail.com> wrote:
>> On Tue, Dec 8, 2009 at 12:17 PM, Daniel Berger <djber... at gmail.com> wrote:
>> > On Tue, Dec 8, 2009 at 5:34 AM, Trans <transf... at gmail.com> wrote:
>> >>  require 'rubygems/specification'
>> >>  NameError: uninitialized constant Gem
>> >>      from /usr/local/lib/site_ruby/1.8/rubygems/version.rb:28
>> >>      from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:7:in
>> >> `require'
>> >>      from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:7
>> >>      from (irb):1:in `require'
>> >>      from (irb):1
>>
>> > I can require it just fine with Ruby 1.8.7 and Rubygems 1.3.5.
>>
>> By chance do you have RUBYOPT set?
>
> No.
>

That reply/question was for Daniel, as he said it worked in his
environment while in mine failed like you.

> If I set it to "-rubygems" of course then it works (in fact
> specification.rb is already loaded then). But I would think loading
> 'rubygems/specification' should work without that --and I am pretty
> sure it used to.

I think it used to...

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry


More information about the Rubygems-developers mailing list