News for hackers. Stuff that matters.
Re:Goop – Dependency Manager for Go by eikenberry on Saturday June 28, 2014 @02:44AM (#7957639)
> Your $GOPATH is a list of directories, not a single directory. This is almost never useful in practice (most people should just use a single directory as their GOPATH).

I disagree. I use and recommend a 2 directory GOPATH setup. The first path being the one where all 'go get' packages are installed and the second being where you put your packages. I've found keeping these separated makes long term management easier.

Re:Goop – Dependency Manager for Go by NateDad on Saturday June 28, 2014 @05:59AM (#7957875)
Why? "my code" is in $GOPATH/src/github.com/natefinch/ ... all code that is not "my code" is in other directories. Why bother having to switch over to some other gopath to get there?

Go import directories, are, by definition, unique. My work code is under github.com/juju/. Why should I put labix.org/v2/mgo under some other root path? They're unique directories either way.