When run, I get:
`require': no such file to load -- rubilicious (LoadError)
But if I comment out the first require, and uncomment the second, it
works. Is there something I can do so that command line scripts don't
have to specify the full path when including library files?
When run, I get:
`require': no such file to load -- rubilicious (LoadError)
But if I comment out the first require, and uncomment the second, it works. Is there something I can do so that command line scripts don't have to specify the full path when including library files?
Thanks,
Joe
Don't you need to require 'rubygems' before requiring a gem?
How does this work? Does the rubygems library replace the "require"
keyword with an implementation that is gem savvy and knows where to look
for them? Does gems always install things in this one standard "place"?
thanks,
jp
Timothy Hunter wrote:
···
Joe wrote:
Don't you need to require 'rubygems' before requiring a gem?
(though technically, 'require' is a method, not a keyword)
matthew smillie.
···
On Jun 2, 2006, at 3:01, Jeff Pritchard wrote:
This is interesting.
How does this work? Does the rubygems library replace the "require"
keyword with an implementation that is gem savvy and knows where to look
for them? Does gems always install things in this one standard "place"?