Here's a suggestion to jar discussion: what about having jgem, jgemupdate, etc that just know how to call the stock scripts? It's not great, but it follows our tradition of prefixing j, it allows those scripts to update independently, and it doesn't break anything for anyone.
So in the release, instead of running "jruby <jruby_home>/bin/gem install rake" you would just run "jgem install rake".
Again, not great, but are there other suggestions?
On 6/12/06, Chris Nokleberg <[EMAIL PROTECTED]> wrote:
On Mon, 12 Jun 2006 11:03:50 -0500, Charles O Nutter wrote:
> We would like to include RubyGems 0.8.11 pre-installed in the next release
> of JRuby. However, there are a few issues with doing that we need to
> resolve:
>
> 1. The scripts RubyGems installs reference 'ruby' directly in their #! line.
> This requires us to call "jruby bin/gem" to invoke them
Not if you symlink the system ruby -> jruby :-)
Seriously, since you use gentoo you're probably aware of "java-config" and
the like. Eventually I think something similar will be needed for
ruby--where cruby and jruby are both first-class implementations that you
can choose from. The script would adjust your environment variables and
the like so that your #! scripts will pick up the right interpreter.
Chris
_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
_______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
