Re: Import gem to Ruby 1.9

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Tanaka Akira wrote:
>> 2. allow gem method to work.  And gem method is usable always.  With
>> yours, it depends on a context of previous LoadError whether a library
>> can use gem method or not.  I don't like this statefullness, too.
> 
> In the IRC session, drbrain said that separating Kernel.gem
> to independent library is possible.  (matz asked it.)
> 
> So my tiny loader will load RubyGems without gem method.
> The statefullness will be removed.

Good.  Now #2 is not the problem.

I cannot see the discussion details held on IRC so I cannot make my
decison whether it's good or not until the change RubyGems team will
make.  But I'm watching svn repository and developer-maillist of
RubyGems and write here when I'll find something to be noted.  Never
mind, let's go ahead.

>> 1. does not have uncertain behavior.  No require 'doc/index' problem I
>> wrote at [ruby-core:12792].
> 
> I agree that mine is not accurate as yours or RubyGems
> itself.
> 
> In contrast, the disadvantage of yours are memory
> consumption and maintenance.

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

> The accuracy and memory consumption is trade off.  For
> accuracy, all gemspecs must be loaded and analyzed.  But it
> consumes memory: analyzer code and loaded gemspecs.
> 
> Since RubyGems itself does accurate analysis, its loader can
> be conservative.  I think memory consumption justify the
> conservativeness.

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.

One additional thought for akr's LoadError fallback.

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.

>> Your proposal of prelude.rb enables RubyGems.  As I wrote, RubyGems uses
>> their 'version selection scheme' independent from whether gem method
>> exists or not.  So you cannot use any other scheme.  RUBYOPT solution
>> allow you to do the above.
> 
> I can install any library under site_ruby.  Does RubyGems
> prohibit it?

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

Regards,
// NaHi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iQEVAwUBRx/zsB9L2jg5EEGlAQKnpgf+NZc9KXPkC4xr1fCsygUeY0xQG+MlLlMg
ftnAuR+j6F6GY2+WfSKH/iaDWpnzFvsI8juqTjmgI5pGcJ2xHl1t88YQ1LMTy2n8
xHGcEQzJL7TCZErb+b2zT8X+PjkYTOJbvA76nfYf9HlY8hoPmQsFlsegkcsfpZvG
3qidHWLIIgG0MfsuWc4MwvV5qk67L9gTh6sG/387jMNHbpGf9lxovz9MgUChnqv0
CMdx9LRdGTSEuszIKqOZLhQD1j9/IIV0LH54yem7sNXB0+b5l8Zun5Oqjli/BdsD
Dx3zEQM3/kQSwLC/dsvjQZcte16VgJ0DVVUxUmeqOvH1Qf4JaJzKhw==
=GGV8
-----END PGP SIGNATURE-----