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

Hi,

Yukihiro Matsumoto wrote:
> We are discussing how we call rubygems after the merge.  Possible
> options are:
> 
>   (a) just merge; if one wants to load libraries from gems, he needs
>       to require 'rubygems' first.  very traditional, but introduces
>       unnecessary normal library/gem'ed library separation.
> 
>   (b) silently require 'rubygems' in initialization process.  rubygems
>       requires a lot of other libraries, so that memory consumption
>       might be an issue.
> 
>   (c) create (or separate) tiny library only for finding gems, and let
>       it be loaded in the initialization (from prelude.rb).  but no
>       one knows how easy/difficult to make such a library (yet).
> 
> How do you think?

I needed to confirm the sense of core team about (c) first.  Sorry not
posting this to ruby-dev first.  I was waiting ko1 posting about this topic.

Matz, ko1 and akr, do you think that (c) includes gem version control,
for example 'gem "soap4r", "1.5.5"' ?  Need to confirm the requirement
of core team first.

Drbrain, sorry about this confusion.  Core team raised an objection to
[ruby-core:11803]
http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-core/11625?11588-12637+split-mode-vertical
at this late date.  They think that gem loading feature should be
enabled by default. (Topic 4-1 arrived to the conclusion (a) above.)
OK, I know it's better than not discussed before imported.  Core team
should have been busy on M17N I think.

I may write my opinion later but basically the intent of RubyGems team
must come first.  We won't be able to maintain rubygems without
cooperation by RubyGems team.

Regards,
// NaHi

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

iQEVAwUBRxCJCR9L2jg5EEGlAQK/Mwf/SBr9A3NhXQZ2UsAy0OmRoBsO/mHnbEfI
Me2Pe0pQF0gLpuFP1m1OrOwghi0XyWnhyZbla1VigjJF6VfLcUeD4LoVjkNrOpkL
sxrNMoEF8kF9Wx1O0EGAXhW9T4tJWTFj0ofXHnyGEUP7JTY9w0vHs5tHLeqDQ71X
QvEIPE8kPuQGbqVvdtgzpsiosFLpwQwucnxxAkssB5jpvCbHxISYQmaKdwJx4WnC
5F33mxeo3RYGAvy2GXJIHGQzoA7vkcOL0raPX84RqQgUdpTr/vZ1GZmIBtMbyskP
SBoNpEBSYu8fgzGFXSyfnPbUVA8r0PPh0+BG1FECwdu55bLaYu9Pnw==
=lRqY
-----END PGP SIGNATURE-----