From: "NAKAMURA, Hiroshi" <nakahiro@...>
Date: 2007-07-24T22:44:53+09:00
Subject: Re: Import gem to Ruby 1.9

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

Hi,

Thanks all for your discussions.  I updated the list with your comments
and mine.

Note that 'ruby' means MRI in this mail.

1. Is platform-specific gem handling needed in ruby/1.9.1?

  - Is binary gem support needed in ruby/1.9.1?
    (Independent from this, RubyGems will support this useful feature)

2. Does RubyGems need some 'require-hook' feature to be added to
   ruby/1.9.1?  What's the requirements?

  - not needed. integrate RubyGems with ruby's require.
  - just bundle RubyGems with ruby as one of a packaging system.
    so hooking -r options as same as Kernel#require is needed.
  - Nobu, I heard that you have once designed this feature halfly.
    Is there anything you can share with us?

3. What gem related commands should be install in BINDIR by the standard
   installer?
     gem, gemlock, gemri, gemwhich, gem_mirror, gem_server,
     index_gem_repository.rb, update_rubygems

  - nothing should be installed
    ('ruby -rgem -e update gemname' should enough)
  - moving everything under the 'gem' command and install only 'gem'
    (some work needed by RubyGems team)

4. What $LOAD_PATH order should be?

  4-1. by default?
    [-I, ENV_RUBYLIB, SITELIBDIR, RUBYLIBDIR, .] or
    [-I, ENV_RUBYLIB, SITELIBDIR, RUBYLIBDIR, ., GEMs]

   - enable RubyGems by default?
   - opt-in?

  4-2. after requiring rubygems?
    [-I, ENV_RUBYLIB, SITELIBDIR, RUBYLIBDIR, ., GEMs] or
    [-I, ENV_RUBYLIB, SITELIBDIR, GEMs, RUBYLIBDIR, .] or
    [-I, ENV_RUBYLIB, GEMs, SITELIBDIR, RUBYLIBDIR, .]

   - the first one is the current RubyGems behavior and it should not be
     changed as far as RubyGems team do not change it.  the behavior
     must have been polished up in several years.
   - maybe I (NaHi) is the only person who have a very hard time with
     this behavior in soap4r-ML.  it's because soap4r is the only lib
     which is gem-ed and located in RUBYLIBDIR.  that's exactly why I
     run this thread.

5. Where's the global repository for bundled rubygems?
   Of course RubyForge should be pointed.

  - we need some 'rather official' repository at www.ruby-lang.org, too.
  - RubyForge plus its mirrors are sufficient.

6. What libraries does RubyGems depend on?
     YAML/Syck, WEBrick, the digest libraries, rbconfig, rdoc, thread,
     optparse, forwardable, time, openssl, open-uri, uri, net/http,
     fileutils, zlib, stringio, socket, tempfile, pathname

  - YAML is used for the gem index and could be dropped in favor of
    marshal.
  - WEBrick is only used for gem_server and not critical.

7. Discussion deadline?

  - vaguely October or so


There're many other interesting topics discussed.  Note that the above
lists are topics related to ruby/1.9.1.  Feel free to post RubyGems
related topic to this list.  It may not make an appeal to RubyGems team
but it will affect a discussion on ruby's require-hook feature.

'What libraries to be unbundled?' will be posted as the new thread soon.

// NaHi

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

iQEVAwUBRqYCOx9L2jg5EEGlAQLekgf+PrvN89MtB8ZkpZHb03RjrT2vkIdCqMPh
6JirtY5qXXHpS4JYX1SUN8bd9E8Z+7NMrPvRoTcfbZ/chsVwH2aKNJRYf/1J2PJ1
CYhzuAtskCvzi2f55PE5EqLDOB3PiTD8alyVxasAdBYs1kLZ9HYGvKvjb589z2Ju
eRdgmaWjeC5YPo0ozeZ7swzYKaQmLPUN0MKpJz2e/hFgqIsxsiyZvZadm++U4xsl
PyqfbhSPf6FgztRgnjdR2CjKUhTuzuWTq8oQ+DKGfaSNbyaFCFLlQYITZwAkxlD7
K7ga7APFbWXU/sAcnBC/hvEmlByeq61VK0GoYJ8Jr5Kdt09LTCFJWw==
=dEVe
-----END PGP SIGNATURE-----