Recommend provisioning Go dev tools, or most any programming language dev tools for that matter, using a simple all task in a conventional makefile.
Be sure to followup your go install... commands with go mod tidy (and modvendor -copy="**/*.h **/*.c **/*.hpp **/*.cpp" in certain Cgo projects).
Try to write only dirt simple go install..., pip3 install..., cargo install... commands in the makefile. That way, your dev provisioning makefile script is more likely to succeed on other platforms.
Optionally, lint the makefile with unmake to detect more portability concerns.
https://github.com/mcandre/unmake
Or, if you happen to be using Go dev tools for non-Go projects, then you may already have a provisioning system available.
For example, shell script projects can provision Go dev tools in a ./script. (You may want to lint these with bashate, ShellCheck, shfmt, and stank.)
For example, C/C++ projects that use a makefile directly and some Go dev tools, may introduce a make provisioning task. Though autotools and cmake projects would want to avoid writing makefiles, which would risks colliding with cmake build files. I guess use shell script provisioning like ./install, or rez, or nobuild, or some other C/C++ provisioning system. The same applies to Perl projects that use makefiles generated from Makefile.PL scripts.
accio extends Go to track buildtime dependencies.
$ cd example
$ which shadow
shadow not found
$ accio -install
$ which shadow
/home/andrew/go/bin/shadowaccio processes packages recursively.
See accio -help for more options.
For more detail on managing Go development packages, see CONFIGURATION.md.
Buildtime dependency tools like golint, Mage, shadow, and so on involve executable artifacts, which go mod unfortunately silently ignores. Fortunately, we have accio to manage these kinds of dependencies.
accio automates away the low level go install commands involved in provisioning reproducible Go build environments.
Notably, accio's own runtime stack is small, requiring no other programming languages or scripts to operate.
FreeBSD
https://godoc.org/github.com/mcandre/accio
https://github.com/mcandre/accio/releases
$ go install github.com/mcandre/accio/cmd/accio@latest$ rm "$GOPATH/bin/accio"For more information on developing accio itself, see DEVELOPMENT.md.
Some tools have not yet updated to use go mod (Go v1.11+ modules) for library dependency management. You can customize the package go111module, e.g. go111module: "off", which activates the corresponding GO111MODULE environment variable configuration for the package.
Go does not support version pins for pre-Go v1.11 module packages.