JRuby masterplan for F19 - RFC

[Vít Ondruch]

Dne 13.12.2012 10:02, Michal Fojtik napsal(a):
> On 12/13, Vít Ondruch wrote:
>> Dne 12.12.2012 18:36, Miroslav Suchý napsal(a):
>>> On 11/29/2012 09:43 AM, Bohuslav Kabrda wrote:
>>>> - Two connected problems: 1) RPM generates auto provides from
>>>> shebangs, e.g. #!/usr/bin/ruby will automatically require ruby
>>>> package; 2) How to run programs with #!/usr/bin/ruby shebangs
>>>> under JRuby?
>>> We already have mechanism for that:
>>>
>>> /etc/alternatives/*
>>> update-alternatives(8)
>>>
>>> /usr/bin/ruby will be symlink to /etc/alternatives/ruby, which
>>> will be symlink to /usr/bin/jruby or /usr/bin/ruby19 (previously
>>> known as /usr/bin/ruby).
>>> And let update-alternatives manage the defaults.
> Maybe a stupid idea, but why we just don't prefix the 'jruby' with 'j'?
>
> So we can have lancher in '/usr/bin/jruby'. Similar for irb, gem...
> (jirb, jgem, etc...)
>
> Then the shebang will be '#!/usr/bin/jruby' and the MRI version can
> cooexist with the jruby.
>
>    -- michal
>

There is probably million of ruby scripts which has some #!ruby shebang. 
If only JRuby is on the system, they'll continue to work. Typical user 
does not care if he runs something by MRI, JRuby or Rubinius. S/he only 
cares if it works.

Actually, I am speaking about typical user, but I personally don't care. 
I don't care if I run gem2rpm by MRI or JRuby, if it works.


Vít