Open sgonyea opened 12 years ago
Thor::Util.ruby_command
should return the currently running ruby command. Rails just happen to be using it for the shebang which makes this is more of a Rails issue. I am unsure how would be best to solve this from Rails side.
This is less an issue, and more of a question.
I generated a rails projects using Rubinius, and later switched to MRI (using RVM) to compare behavior... But what happens is:
Reason being, the "script/rails" command looks like:
Notice line 1--it expects "rbx" to be my ruby executable.
What's nice about RVM is that it makes switching between rubies to be pretty transparent; had I created the rails project using MRI, I'd have never noticed the issue.
Are there any thoughts on how best to handle this? Or, a better way to phrase it: Who's problem is this?
It's a trivial issue, but it's tedious to debug and may be discouraging for people playing with non-MRI rubies.
Would a patch be accepted, that allows an ENV variable to override whatever is in RbConfig? Or, because this uses RbConfig, should RVM / rbenv be responsible for configuring this at compile time? Or should I just buzz off? :)
If nothing else, this issue will show up on Google and save that small group of people some time. Feel free to close this issue whenever.