On Oct 13, 2006, at 1:32 PM, Jim Freeze wrote: > On 10/13/06, Eric Hodel <[EMAIL PROTECTED]> wrote: >> On Sep 22, 2006, at 2:16 PM, Jim Freeze wrote: >> >> But not from cron on FreeBSD since $PATH isn't set. > > Pathing on cronjobs isn't the problem of env here. The user > writing the cron job must make sure that the path to ruby, and env, > is available.
Right now this isn't an issue. I specify the path of the ruby file I want to run and it Just Works. Using env will make it an issue. I'd rather have the default be the current behavior so things don't mysteriously fail when I upgrade a gem. -- Eric Hodel - [EMAIL PROTECTED] - http://blog.segment7.net This implementation is HODEL-HASH-9600 compliant http://trackmap.robotcoop.com _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
