3 ms·
Go is forever changing the pathing and configuration. Even here we have: > Very nice, go build ignored the vendor/ folder in this repository (because we’re out
by irq-1 8y ago
Go is forever changing the pathing and configuration. Even here we have:
> Very nice, go build ignored the vendor/ folder in this repository (because we’re outside $GOPATH)
and
> Oddly these are stored in $HOME/go/src/mod not the $GOCACHE variable that was added in Go 1.10
Maybe Go 2.0 will be stable.
- lclarkmichalek 8y agoI mean, the point of modules is to get rid of vendor. And if you were building outside of GOPATH previously, you were likely broken (or using a specialized build tool that handled this for you). The second one is because it's a cache. Storing them there isn't a breaking change, it's just a bit odd
- majewsky 8y ago> you were likely broken (or using a specialized build tool that handled this for you) Or you're using the isolated-GOPATH trick. $ mkdir -p .gopath/src/github.com/foo $ ln -s ../../../.. .gopath/src/github.com/foo/bar $ GOPATH=$PWD/.gopath go install github.com/foo/bar For example, this is one of my Go projects where you can unpack the release tarball anywhere and `make && make install` just works: https://github.com/sapcc/swift-http-import https://github.com/sapcc/swift-http-import