[Rubygems-developers] Oddity in Gem.activate?

[Gavin Sinclair]

My informal test shows something funny:

  $ irb --simple-prompt
  >> require 'rubygems'
  => true
  >> Gem.activate('rake', true)
  => true
  >> puts $LOAD_PATH
  /usr/local/lib/ruby/gems/1.8/gems/rake-0.4.10/bin
  /usr/local/lib/ruby/gems/1.8/gems/rake-0.4.10/lib
  /usr/local/lib/ruby/site_ruby/1.8
  /usr/local/lib/ruby/site_ruby/1.8/i386-cygwin
  /usr/local/lib/ruby/site_ruby
  /usr/local/lib/ruby/1.8
  /usr/local/lib/ruby/1.8/i386-cygwin

Why is the _bin_ path of the Rake gem being added to the $LOAD_PATH?
Shouldn't it just be the _lib_ directory?

Gavin