From: Eric Hodel <drbrain@...7.net>
Date: 2007-07-12T05:55:15+09:00
Subject: Re: Import gem to Ruby 1.9

On Jul 10, 2007, at 15:52, Tim Morgan wrote:
> On 7/9/07, Eric Hodel <drbrain@segment7.net> wrote:
>> On Jul 8, 2007, at 00:49, SASADA Koichi wrote:
>>> Matz plans to import gem into Ruby 1.9.  Does anyone has any  
>>> comment to this?
>>
>> RubyGems is still missing one key feature, the ability to handle
>> platform-specific gems.  There may be a few other minor features that
>> are missing, but I don't think RubyGems is ready for inclusion until
>> then.
>
> Is this feature planned for the near term?

Its in the bug tracker.  RubyGems also wants to be in -core, but  
nobody has bothered to spare the time to write it until recently,  
when somebody on the RubyGems mailing list indicated they were  
working on a patch.

>> Also, RubyGems can make releases faster than Ruby can, so it should
>> still be possible to upgrade RubyGems to never versions independent
>> of Ruby.
>
> Perhaps RubyGems could be shipped with Ruby core, as a stub.

There's a small change to #require that needs to be made to invoke  
the bit of RubyGems that does $LOAD_PATH manipulation.  So long as  
that is as small as possible, the default $LOAD_PATH should allow a  
RubyGems in site_ruby to override the one in the standard library.

> This would allow a basic functionality to bootstrap new gems as  
> they are released, including RubyGems itself.
> If Gems are such a great solution, perhaps Core Libs could be  
> repackaged as gems as well.
> This could achieve a new agility to Ruby itself.

I believe this idea floated into the heads of one of the other  
RubyGems maintainers.  Possibly, its also been discussed, but I forget.

--
Poor workers blame their tools. Good workers build better tools. The
best workers get their tools to do the work for them. -- Syndicate Wars