This project is archived and is in readonly mode.
Scripts in script dir only run with "ruby" command in path
Reported by Charles Oliver Nutter | March 1st, 2009 @ 12:08 AM | in 2.x
All the scripts in the script dir have a shebang line of #!/usr/bin/env ruby which prevents running them directly when the "ruby" command on a system is not "ruby". For example, JRuby's command is "jruby" and I also have ruby1.9 installed as "ruby1.9".
If these scripts were generated, based on the actual name of the Ruby command being run, then they could be directly executed no matter what implementation or executable name the user was using.
I do not have a patch for this because I'm not yet familiar enough with the generators.
Comments and changes to this ticket
-
Jeremy Kemper March 1st, 2009 @ 12:46 AM
- State changed from “new” to “wontfix”
/usr/bin/env ruby means the app is portable to other environments. You can still invoke the scripts using the ruby of your choice.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Jeremy Kemper