rbinstall.rb: install both src and batch files separetely
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:
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:
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.
#6 [ruby-core:50053] Updated by Luis Lavena almost 4 years ago
- Target version changed from 2.0.0 to next minor
Sorry, was unable to work on this while still working on the other bug/issues.
I'm moving this to next minor.
Either way, RubyInstaller binary distributions have been doing what this ticket describes.
#7 [ruby-core:50054] Updated by Yusuke Endoh almost 4 years ago
Though it is better if it is implemented in this month, an accepted feature can be implemented up to code freeze (around Christmas).
If you are still having difficulties, it is okay to postpone to next minor.
Yusuke Endoh firstname.lastname@example.org