Yes sorry that was badly phrased. Should have been Setting gopath...
I'm confident they will gradually get rid of it. It was a convenient crutch at first but for those outside a mono repo quite limiting.
Re:Go 1.8 Release Notes
by libeclipse on Thursday February 16, 2017 @11:52PM
(#13666022)
Is this likely to happen?
Re:Go 1.8 Release Notes
by shadowmint on Friday February 17, 2017 @06:26AM
(#13667482)
The tracking issue is here: https://github.com/golang/go/issues/17271
Maybe? I think broadly the answer is yes, but not very soon.
It'll probably be a timeline like:
- Sometime between now and 1.10 / 1.11 - allow vendor outside of GOPATH
- 1.11 / 1.12 - dep formally becomes part of the go toolchain
- 1.12+ ?? - GOPATH stops existing or significantly changes form.
Nothing is going into 1.9; it's not ready yet even as a candidate feature. 1.10 could see some changes, and beyond that there will definitely be some kind of changes.
...but probably not this year.
If you're using anything in a vendor folder, you still need to set GOPATH to a parent folder of your /src/project.
ie. `vendor` is still ignored if it is outside GOPATH; and if you don't set GOPATH, it just defaults to `$HOME/go`. If you ignore GOPATH and don't set it, your code won't build.
You still need GOPATH for now.
(once vendor can exist outside of GOPATH we can really start moving forwards with things)