I have similar problems building Go apps for internal use. My solution so far is to use per-project $GOPATH and `git subtree` to manage the whole $GOPATH as a s

I have similar problems building Go apps for internal use. My solution so far is to use per-project $GOPATH and `git subtree` to manage the whole $GOPATH as a single repository. The primary benefit of doing so is build repeatability: any dev can `git clone` the repo and build the app successfully after setting the $GOPATH to the repo directory. Changes in external dependencies have no affect on us until we manually incorporate them into our repo via `git subtree`. There is no need to `go get` and we avoid its associated problems (e.g. versioning, availability of remote repos, etc).