In article <4718708D.3050001 / sarion.co.jp>,
  "NAKAMURA, Hiroshi" <nakahiro / sarion.co.jp> writes:

> To decide what directories should be added to $LOAD_PATH, we need to
> check Gem::Specifications in specification directory.  ruby-debug gem
> defines 'cli' directory as a requrie_path for example.  Here's an
> implementation what should be done by 'gem load only' gem handler.
> http://dev.ctor.org/vtr
> It supports version control but it should be removable easily.

Oh, I didn't know that.  Thank you for the information.
However I don't like loading all gemspecs.

Since the condition can be conservertive, the glob can be changed to 
  Dir.glob(".../lib/ruby/gems/1.9/gems/**/#{feature}*")
for supporting such libraries.

Do you know a library which cannot be supported by the glob
above?

> Matz, akr, and ko1, you wamt to just include Kernel.require of rubygems
> and no Kernel.gem and version control, right?  What is different from
> just installing files to site_ruby dir then by rpm or deb?  What is the
> point you want to include from rubygems?

Someone might install a library as gem.  I don't want to
care the library is installed as gem or not.  This is my
reason.  Is it not enough?
-- 
Tanaka Akira