From: "NAKAMURA, Hiroshi" <nakahiro@...>
Date: 2007-10-23T10:24:12+09:00
Subject: Re: Import gem to Ruby 1.9

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

Hi,

Tanaka Akira wrote:
> In article <471CAFE0.2070104@sarion.co.jp>,
>   "NAKAMURA, Hiroshi" <nakahiro@sarion.co.jp> writes:
> 
>> My opinion on the basis that enabling rubygems by default is, allow to
>> load gemspecs for creating feature manifest.  It's better than
>> 'wild-guessing-and-load-rubygems-then-pray-it's-included' for me.  Oh
>> man, I must not be able to express my mind correctly in English.
> 
> I'm not sure what you want.

It means;

require 'gemloader'

in prelude.rb, if we need to enable gem loading by default.

Bear in mind that my vote is RUBYOPT (not enable rubygems by default).

>> RubyGems offers versions control unlike this kind of static version
>> dependency solving by administrator.  It offers dynamic version
>> dependency solving at runtime.  Say rails-1.2.3 and rails-1.2.5 are
>> installed on a system.  There also be activerecord-1.15.3 and 1.15.5.
>> One Rails application runs with rails-1.2.3 + AR-1.15.3 and another
>> application runs with rails-1.2.5 + AR-1.15.5.  Even granting that we
>> don't offer gem method by default, rubygems loads feature in a different
>> manner.  I think you might not like this behavior.
> 
> I think I like it.

But gem method is not important for you?  Why don't you add gem method
fallback to prelude.rb as well?

Regards,
// NaHi

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

iQEVAwUBRx1NHh9L2jg5EEGlAQIF2gf8DngH2ShVIwoQnzAK36UQhnuFuJeulcJE
cql04msOb1bGLc7aiMQsrJ359f2yHJPgDqN/YNIrkg87JIwo3VY08OknKGCioTE0
/fzosQUuXFzdHD7McivEkphUkzMUJxD83ZqMTfscG3bYwPdakyR9xGQ3srrT4J3j
Mf74zZDMJ+MwIj3J/6dg/o99w6SLrFF5A/BdsTb9zDUFezELT4UtrNe+BykzQ53C
6KkyU3Y7556q6wLC2Yq/Ff9pgmnU8WI+L+eyRFeP9YBJjb9VhpuMyevUPgY0S5TA
v3RULTNo5kWFn2EUq3eh84TGgo+fTPsByGAnAYs2zdi/otX9W/wUhQ==
=egbm
-----END PGP SIGNATURE-----