Dne 9.10.2012 08:19, Bohuslav Kabrda napsal(a):
And one more comment about the jgem. I am asking myself if that is
good
idea to provide such jruby specific executables (although jgem might
be
good candidate for exception), since it would imply that every gem
has
to have its executable for different Ruby implementations etc.
However,
I believe, that user is not interested which interpreted is used to
execute his program, as long as he gets the result. Therefore, the
distinction between gem and jgem is just implementation detail IMO
and
should not be exposed, (but I might be proven wrong ;).
I don't agree with you here. Consider our way of local installation - user runs "gem install foo" and that installs the foo gem into his
home directory. But that would only install the MRI version of the gem. For installing JRuby version, the user would be forced to run "jruby
/usr/bin/gem" - that is why I would prefer "gem-jruby". As for the "*-jruby" executables, I would vote for providing the
"core" ones: "gem-jruby" and "irb-jruby".
Yes, that was exactly why I mentioned that jgem/gem-jruby might be
candidate for exception ;)
BTW, isn't there for JRuby something like in Rubinius, such as you can
call "rbx -S rake" to execute rake, so you don't have to specify full
path to script.
Vit
_______________________________________________
ruby-sig mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
