You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.
Currently, each tool is installed using go install command which will name the executable after the folder it is located in. For example, if main.go is in .../cli/main.go and is installed, the name of the binary will be cli. Therefore, there is a possibility for a clash if more than one tool is contained in a folder of the same name.
Solution
Allow for (optional) custom naming of each tool set in the tools.json
The text was updated successfully, but these errors were encountered:
pgt502
changed the title
Allow for custom naming of the executables and additional params when installing
Allow for custom naming of the executables
Jan 16, 2019
Currently, each tool is installed using
go install
command which will name the executable after the folder it is located in. For example, ifmain.go
is in.../cli/main.go
and is installed, the name of the binary will becli
. Therefore, there is a possibility for a clash if more than one tool is contained in a folder of the same name.Solution
Allow for (optional) custom naming of each tool set in the tools.json
The text was updated successfully, but these errors were encountered: