On Oct 15, 2006, at 8:35 AM, Jim Freeze wrote: > On Oct 15, 2006, at 1:23 AM, Eric Hodel wrote: >> On Oct 13, 2006, at 1:32 PM, Jim Freeze wrote: >>> 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 think the issue is when someone installs a gem and wants to run > a ruby executable from that gem under different versions of Ruby. > Hard pathing in the shebang will not work in this case. The only > alternative > is to use env.
Granted, but I think this is the less-common scenario. >> I'd rather have the default be the current behavior so things don't >> mysteriously fail when I upgrade a gem. > > I think that has already been stated. The default won't change, > that is why I suggested a couple of option flags. I must have I missed it, apologies. I don't have problems with new flags to accommodate multiple versions/ platforms. The ones you proposed look fine to me. -- 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
