go-tools installs a binary called 'bundle' that conflicts with the Ruby gem of the same name

[DanHam (Dan)]

$ port provides /opt/local/bin/bundle
/opt/local/bin/bundle is provided by: go-tools

The naming conflict has been raised with the Go developers.

According to ​this GitHub issue/comment the Go-tools bundle binary is only intended for use internally within the Go project itself. ​This comment suggests not packaging the bundle binary with Go-tools at all.

[mf2k (Frank Schima)]

In the future, please add the port maintainer(s) to Cc (port info --maintainers go-tools), if any.

[mascguy (Christopher Nielsen)]

I can confirm this is still an issue, as I was just bitten by it after using port select to choose a default Ruby: The operation overwrites /opt/local/bin/bundle with a Ruby symlink, without warning.

In order to fix, one must first unselect Ruby, and then deactivate/activate go-tools.

I'm wondering if this is a bug - or at least, undesirable behavior - of port select? Ideally it should fail with an error, rather than overwriting anything. Thoughts?

[mascguy (Christopher Nielsen)]

PR created to fix:

​https://github.com/macports/macports-ports/pull/12501

[Christopher Nielsen <mascguy@…>]

In bffdd87166d0d2ac6126f45c1b0028244425e963/macports-ports (master):

go-tools: eliminate conflict with Ruby

• Delete internal binary 'bundle'

Fixes: #57787

[herbygillot (Herby Gillot)]

In 7604f34da05f1f2a953abdd4d250ea4ae56d4f23/macports-ports (master):

go-tools: update to 0.1.8

• restore and *rename* the bundle binary, instead of wholesale deleting it

See: #57787