At 8:47 AM +0000 4/6/08, M C wrote:
>4) Please re-consider the naming of rake, spec, gem and ri tasks in the bin 
>directory. I would like to co-exist with a normal ruby installation so the 
>first thing I normally do after installing jruby is to rename them all to 
>jrake, jspec, jgem, jri etc. so that I f.x. get MRI's gem when I type "gem" 
>and jruby's gem when I type "jgem". The topic has been brought up before and I 
>know there is resistance to this I just never understood why ?

The renaming would have to be integrated into rubygems -- any gem can install a 
command line program so your list: jrake, jspec, jgem, jri ... etc would have 
to also include any other command line program installed by rubygems running 
under jruby -- jrails, jhaml ... etc.

Some gems compile libraries as part of their install. Hpricot installed under 
MRI compiles native C libraries while under JRuby it uses a Java library 
distributed in a jar. In general once Gems that require native code (I'm 
included Java code as one of the native code examples) are installed they 
expect to only be used with that os/arch.

Coexistence for me means that none of my MRI and JRuby gems or libraries 
overlap and that when I want to, for example run rake in JRuby I use: jruby -S 
rake.

In the past when I wanted to work in JRuby I used to put the path 
JRUBY_HOME/bin as the first element in my $PATH environmental variable.  This 
would allow me to run  all the command line ruby programs installed by gems by 
just typing the names -- but it made it much harder to switch back and forth 
between C Ruby and JRuby.

Now I use the guidelines described here:

  http://wiki.jruby.org/wiki/Getting_Started


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to