[ruby-core:91183] [Ruby trunk Bug#15550] RubyGems bin files - from two to one...

[ruby-core:91183] [Ruby trunk Bug#15550] RubyGems bin files - from two to one...

[Greg.mpls]

Issue #15550 has been reported by MSP-Greg (Greg L).

----------------------------------------
Bug #15550: RubyGems bin files - from two to one...
https://bugs.ruby-lang.org/issues/15550

* Author: MSP-Greg (Greg L)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.7.0dev (2019-01-19 trunk 66872) [x64-mingw32]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
As I recall, ruby-loco is no longer touching the gem related files located in the bin folder.  Previously, there were two files associated with each gem, one with a .cmd/.bat extension, one without.

Currently, there is just one file with a .cmd extension.  I have seen this before, and just came across it again, where gems are using *nix scripts run with either the MSYS2 shell or the Git shell in their CI.  Hence, there is an expectation for the plain (extensionless) file to exist.

Not sure if this is considered a breaking change or a bug/issue.

Thanks, Greg



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

[ruby-core:91191] [Ruby trunk Bug#15550] RubyGems bin files - from two to one...

[Greg.mpls]

Issue #15550 has been updated by MSP-Greg (Greg L).


An easy way to repo this is to open the Git bash shell, and run `bundle version`.  I got an error message of:

```
bash: /c/Greg/Ruby99-x64/bin/bundle: No such file or directory
```

I believe the MSYS2 shell changes PATH, the Git Bash shell does not.  Or, `ruby -v` works in Git, but not MSYS2...

----------------------------------------
Bug #15550: RubyGems bin files - from two to one...
https://bugs.ruby-lang.org/issues/15550#change-76424

* Author: MSP-Greg (Greg L)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.7.0dev (2019-01-19 trunk 66872) [x64-mingw32]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
As I recall, ruby-loco is no longer touching the gem related files located in the bin folder.  Previously, there were two files associated with each gem, one with a .cmd/.bat extension, one without.

Currently, there is just one file with a .cmd extension.  I have seen this before, and just came across it again, where gems are using *nix scripts run with either the MSYS2 shell or the Git shell in their CI.  Hence, there is an expectation for the plain (extensionless) file to exist.

Not sure if this is considered a breaking change or a bug/issue.

Thanks, Greg



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

[ruby-core:91884] [Ruby trunk Bug#15550] Windows - gem bin files - can't run from bash shell

[hsbt]

Issue #15550 has been updated by hsbt (Hiroshi SHIBATA).

Assignee set to hsbt (Hiroshi SHIBATA)
Status changed from Open to Assigned

----------------------------------------
Bug #15550: Windows - gem bin files - can't run from bash shell
https://bugs.ruby-lang.org/issues/15550#change-77205

* Author: MSP-Greg (Greg L)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
* ruby -v: ruby 2.7.0dev (2019-01-19 trunk 66872) [x64-mingw32]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
As I recall, ruby-loco is no longer touching the gem related files located in the bin folder.  Previously, there were two files associated with each gem, one with a .cmd/.bat extension, one without.

Currently, there is just one file with a .cmd extension.  I have seen this before, and just came across it again, where gems are using *nix scripts run with either the MSYS2 shell or the Git shell in their CI.  Hence, there is an expectation for the plain (extensionless) file to exist.

Not sure if this is considered a breaking change or a bug/issue.

Thanks, Greg



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