----- Original Message -----
Dne 4.12.2012 15:54, Bohuslav Kabrda napsal(a):
> I have just pushed all of this stuff into my testing repo [1] (the
> /usr/bin/ruby stub, modified MRI Ruby, etc.), so you can test that
> now. For me, it seems to work. I call the stub "multiruby"
> (actually
> Vit's idea :) ) and its upstream is at [2] (no fancy git tags and
> stuff, I just made it work for now...). By default, the stub uses
> MRI.
I should also point out that you can try to use different rubies such
as:
$ ruby _mri_ -v
$ ruby _jruby_ -v
Slavek, any indea if we could provide some help? Something like "ruby
_help_" for example? However I am not sure if anybody is able to find
this command :/
Vít
I think I could add a hook for -h, that would first print help for the multiruby script
and then keep running for the used interpreter. So something like
$ ruby -h
This is Fedora's multiruby executable. You can blah blah blah...
Currently available runtimes: _mri_ (default), _jruby_
Selected: _mri_
<actual help for MRI>
I think this shouldn't affect the performance and it shouldn't damage user
experience.
Does that sound sane?
--
Regards,
Bohuslav "Slavek" Kabrda.