Not sure, I am very much new to the new "go" command and how it works. Everytime I did a go get on a repo it would get the wrong version. I'd just cd into the 3rdparty dir and then pull/checkout the weekly branch and be ok.
I figured their had to be a better way but I was pretty focused on getting projects done.
And to be specific this was on non-standard libraries the standard libraries provided by go worked out of the box.
The go command will use the right version but only if the person writing the library has bothered to tag the version to use. Many people don't. Part of the point of Go 1 is to stabilize the language. We're committing to slowing down the rate of churn and to not changing the APIs in backwards incompatible ways for the lifetime of Go 1 (1.1, 1.2, and so on), so now there should be much less problem with just using tip/HEAD/whatever in the repositories without tags.
I figured their had to be a better way but I was pretty focused on getting projects done.
And to be specific this was on non-standard libraries the standard libraries provided by go worked out of the box.