[Rubygems-developers] Config clash

Richard Kilmer rich at infoether.com
Wed Sep 15 00:03:33 EDT 2004

On 9/14/04 10:46 PM, "Gavin Sinclair" <gsinclair at soyabean.com.au> wrote:

>> On Tue, 14 Sep 2004 22:33:09 -0400 (EDT), Gavin Sinclair
>> <gsinclair at soyabean.com.au> wrote:
>>> I've just dicovered an anti-social behaviour of RubyGems.  I'm mucking
>>> around with 'acoc' (look on RAA).  It defines a class called Config:
>> mmm. I think that this is really a problem with acoc. It is still
>> developed (last update 2004/04/05). acoc shouldn't be creating a class
>> "Config", it should be doing something like:
>> module Acoc
>>   class Config < Hash; end
>>   :
>>   : # The rest of the Acoc module.
>> end
>> exit Acoc.run(...)
>> This is the sort of thing that RPA will be good at handling.

And now so is gems...

> I agree that acoc should do something like that.  But I don't think that
> absolves RubyGems of responsibility.
> Gavin

The rbconfig.rb file is now read and module_eval'd into the Gem module in
the rubygems.rb file.  This keeps the Config module in the Gem namespace
instead of the root.  This should then allow the acoc library to work...if
you could check that out it would be cool.



More information about the Rubygems-developers mailing list