Charlie,
I think rubygems has just the option for us:
-E, --[no-]env-shebang Rewrite the shebang line on installed
scripts to use /usr/bin/env
But it didn't work for me earlier today when I upgraded rubygems for
JRuby from 1.1 to 1.1.1, for some reason.
Well, the upgrade from 1.1.0 to 1.1.1 was a bit unusual altogether,
since the following command just did nothing, refusing to upgrade:
jruby -S gem update --system --env-shebang --no-rdoc --no-ri
So, I first downgraded to rubygems 1.0.1, and then upgraded to 1.1.1
successfully.
Thanks,
--Vladimir
On Mon, Apr 28, 2008 at 4:40 PM, Charles Oliver Nutter
<[EMAIL PROTECTED]> wrote:
> JRuby ships with its "jruby" command as a shell script or batch file under
> Windows. This means that the default behavior for JRuby installing RubyGems
> is to always use an "env" shebang. However there are two problems with this
> right now:
>
> - we have to manually patch our copy of RubyGems every time we upgrade, to
> make sure it env-shebangs by default
> - RubyGems hardcodes the env shebang string to "ruby" rather than using the
> name of the current runtime's command (this may have been fixed?)
>
> At any rate, I'm looking for suggestions or a RubyGems fix that will save
> us having to manually patch this all the time. JRuby is not going to have a
> native startup command any time soon, so the env shebang is always going to
> be necessary.
>
> Thoughts?
>
> - Charlie
> _______________________________________________
> Rubygems-developers mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
