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 was archived by the owner on Sep 9, 2020. It is now read-only.
What version of Go (go version) and dep (git describe --tags) are you using?
E:\Installs\go-tools\src\github.com\golang\dep (master)
λ go version
go version go1.8.3 windows/amd64
E:\Installs\go-tools\src\github.com\golang\dep (master)
λ git describe --tags
v0.3.0-162-gf134697
What dep command did you run?
E:\workspace\golang\src\github.com\golang\dep (master)
λ dep ensure
What did you expect to see?
I like to differentiate the Go tools I use with Go like gometalinter and install them to a separate location than %gopath%. I did the same with dep(installed to E:\Installs\go-tools). I was expecting that the cache would be stored in this Go workspace(E:\Installs\go-tools\pkg\dep).
What did you see instead?
The cache was generated in %gopath%/pkg/dep and not relative to the actual installation path of dep. While this is by no means a serious issue, this can negatively affect performance for anybody who uses multiple go workspaces. I think it will be better to have a cache location which is independent of the %gopath%. I apologise if this is a known limitation or if it has been reported already.