5 ms·
Just because you have a Makefile in your repository, it doesn't mean the package(s) aren't `go get`-able. As long as the package can be built with `go install`/
by insertnickname 9y ago
Just because you have a Makefile in your repository, it doesn't mean the package(s) aren't `go get`-able. As long as the package can be built with `go install`/`go build` it should be fine.
- jerf 9y agoAnd there are cases where it is simply impossible for the package to be installed simply with "go get" or "go install". C'est la vie. The idea is not to unnecessarily introduce dependencies on things like make, not that you can remove the necessary dependencies on external tools.
- tptacek 9y agoRight, but then the value of the Makefile is pretty marginal.
- jeffinhat 9y agoThe value of the Makefile is for automating repetitive dev tasks. Consumers of a golang CLI should use `go get` but this makes it easier for contributors who run tests, cut releases, .. The authors example is clean/simple. Here's an example not so clean/simple example where we needed to do more complex stuff like build for all target platforms[1]. [1] https://github.com/cloudfoundry-community/stackdriver-tools/blob/master/src/stackdriver-nozzle/Makefile https://github.com/cloudfoundry-community/stackdriver-tools/...