From: Tanaka Akira <akr@...>
Date: 2007-10-25T12:02:17+09:00
Subject: Re: Import gem to Ruby 1.9

In article <471FF3B1.3060103@sarion.co.jp>,
  "NAKAMURA, Hiroshi" <nakahiro@sarion.co.jp> writes:

> Don't list 'maintenance' here.  When it's good enough, RubyGems team
> will do it as I wrote in [ruby-core:12810].

The maintenance problem is too important to ignore.

I couldn't find a mail to mention RubyGems developper will
do it.  Point me it.  Or, is it private discussion between
you and RubyGems developper?

> We've written our thought on this trade off many times each other,
> without concrete grounds.  I still don't have any number to show so I
> don't repeat writing my thought on this again. :-)  No other comments
> from ruby-core.  The decision is up to core team now.

I don't know the definition of "core team".  What is it?

> Issue #1 is for solving the problem how we map feature -> path to be
> added to $LOAD_PATH.  Java uses MANIFEST in jar.  RubyGems uses gemspec
> in spec dir.  akr's LoadError fallback uses file system wild globbing.
>  Default Ruby require uses file system accurately.
>
> Can gem command of RubyGems can create a MANIFEST in gemspec dir?  Then
> akr's LoadError fallback can grep it for finding rubygems to be loaded
> or not.  It won't be needed as a part of RubyGems though.
>
> akr, let me hear your thought on this.

I'm happy to use such information if RubyGems provide it.

> I mean that you can use site_ruby but cannot use others.

I think I can use RubyGems if I install a library as gem.
I don't understand what you mean.
-- 
Tanaka Akira