Issue #6769 has been updated by usa (Usaku NAKAMURA).


IMO, it's okay.
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-28286

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: usa (Usaku NAKAMURA)
Category: misc
Target version: 2.0.0


=begin
Hello,

Current behavior of rbinstall.rb is to concat bin scripts (erb, rake, rdoc, etc) along with a batchfile stub in a single file, resulting in erb.bat, rdoc.bat etc.

Those files works OK when invoked directly, but they do not support the following scenarios:

* Invoke it like "ruby -S rake", which looks for extension-less script in the path (and that does not exist)

* Cannot invoke those scripts from another script, example, from Rake, do "ruby 'rdoc'" will not work.

To circumvent this issue at RubyInstaller, we copied the original bin scripts and replaced the batchfile stubs with simple ones:

https://github.com/oneclick/rubyinstaller/blob/master/recipes/interpreter/ruby19.rake#L188-197

===

I would like to change rbinstall.rb to copy over verbatim bin scripts and simple batchfiles stubs.

That will solve the above two issues I mentioned plus open the scenario to a easy executable-based launcher, similar to gem-exefy:

https://github.com/bosko/gem-exefy

To have identifiable scripts in list of process plus, customized firewall rules and remove the dreaded "Terminate batch job" prompt.

Before I start working on this, I wanted to know what do you think about this?

Thanks in advance for your feedback and looking forward your responses.
=end



-- 
http://bugs.ruby-lang.org/