Brian Candler wrote:
> Or simpler: only put "require 'rubygems'" at the top of scripts which 
> use rubygems.
> 
> (Obviously less convenient than using RUBYOPT of course, but your script 
> may be more portable)

Except I'd rather not have to guess/remember which things are installed 
as gems, and do it correctly on each host I'm running the script on. So 
the require hack figures that out for me. (We do some embedded work on 
smartphones, gumstix, and geode, so some of our systems don't use gems 
at all.)

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407