News for hackers. Stuff that matters.
Re:Best practices for a new Go developer by pzduniak on Wednesday September 02, 2015 @11:10AM (#10159737)
The package versioning issue has been solved in 1.5 for most of the popular use cases with the vendor experiment. Works just fine for me!
Re:Best practices for a new Go developer by drakenot on Wednesday September 02, 2015 @02:35PM (#10161153)
I hadn't heard about the vendor experiment. Is it now possible to point at individual tags/branches of a remote repository?
Re:Best practices for a new Go developer by lobster_johnson on Wednesday September 02, 2015 @03:24PM (#10161397)
The new "vendor" system is basically that the Go compiler will look in vendor/ for your import before trying to traverse the GOPATH. This means you can manually download and freeze dependencies there. However, Go leaves the management of this vendor directory to you or some hypothetical helper tool — or with git submodules, for that matter. "go get", for example, still works just like before (ie., stores stuff in $GOPATH/src).