I've written a library that I plan to distribute as a RubyGem, but I
think it's a little crazy to require all users of this library to do
require 'rubygems' # or RUBY_OPT="-rubygems"
require_gem 'oscar'
Can't I tell RubyGems to install my gem straight to the RUBY_LIB
directory instead of having it go into its own separate folder?
Ideally, users should install my library and then just do "require
'oscar' "
I think the separate folders are fine for applications, but for
libraries, I don't really see how they help.
Bill
···
--
$stdout.sync = true
"Just another Ruby hacker.".each_byte do |b|
('a'..'z').step do|c|print c+"\b";sleep 0.007 end;print b.chr
end; print "\n"
I've written a library that I plan to distribute as a RubyGem, but I
think it's a little crazy to require all users of this library to do
require 'rubygems' # or RUBY_OPT="-rubygems"
require_gem 'oscar'
Can't I tell RubyGems to install my gem straight to the RUBY_LIB
directory instead of having it go into its own separate folder?
No. You can't. We used to install stubs, but they were messy, so we
took it out. We've also discussed (since RubyConf, actually) the idea
of doing a "gem deploy" or something like that which would move a
gem'd version of an installed lib to the RUBY_LIB directory. We
obviously still haven't done this. If you're interested in this
feature and have some free time, patches are welcome.
Ideally, users should install my library and then just do "require
'oscar' "
Yea, that's what the RUBYOPT thing is for.
···
On Mon, 7 Feb 2005 14:42:33 +0900, Bill Atkins <batkins57@gmail.com> wrote:
