Forum: Ruby-core [ruby-trunk - Feature #6769][Assigned] rbinstall.rb: install both src and batch files separetely

Issue #6769 has been reported by luislavena (Luis Lavena).

----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769

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/mas...

===

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

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/mas...

===

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

Issue #6769 has been updated by luislavena (Luis Lavena).

Assignee changed from usa (Usaku NAKAMURA) to luislavena (Luis Lavena)

Thank you Usa, will work on this.
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-28391

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
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/mas...

===

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

Issue #6769 has been updated by ko1 (Koichi Sasada).


ping.
status?

----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-31706

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
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/mas...

===

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

Issue #6769 has been updated by luislavena (Luis Lavena).


ko1 (Koichi Sasada) wrote:
> ping.
> status?

Replied in [ruby-core:48192], still working on a patch, might show some 
progress this weekend.
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-31717

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
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/mas...

===

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

Issue #6769 has been updated by mame (Yusuke Endoh).


Luis, what's the status?

--
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-33697

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
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/mas...

===

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

Issue #6769 has been updated by luislavena (Luis Lavena).

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.

Thank you.
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-33829

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
Category: misc
Target version: next minor


=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/mas...

===

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

Issue #6769 has been updated by mame (Yusuke Endoh).


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.

Thanks,

--
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Feature #6769: rbinstall.rb: install both src and batch files separetely
https://bugs.ruby-lang.org/issues/6769#change-33830

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
Category: misc
Target version: next minor


=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/mas...

===

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