Thanks. Now I get a console full of: thing.go:10:2: cannot find package "whatever/thing/frob" in any of: /usr/lib/go-1.7/src/whatever/thing/frob (from $GO

Thanks. Now I get a console full of: thing.go:10:2: cannot find package "whatever/thing/frob" in any of: /usr/lib/go-1.7/src/whatever/thing/frob (from $GOROOT) ($GOPATH not set) So I go looking for GOPATH documentation, and it tells me I need to put all my source dependencies in one directory. That's unlike everything else on the planet, but OK. I do that, and set GOPATH=~/go. Now: thing.go:10:2: cannot find package "whatever/thing/frob" in any of: /usr/lib/go-1.7/src/whatever/thing/frob (from $GOROOT) /home/ctz/go/src/whatever/thing/frob (from $GOROOT) ($GOPATH not set) OK, so do I need to set GOPATH as well? thing.go:4:2: cannot find package "bytes" in any of: /home/ctz/go/src/bytes (from $GOROOT) ($GOPATH not set) thing.go:8:2: cannot find package "container/list" in any of: /home/ctz/go/src/container/list (from $GOROOT) ($GOPATH not set) That seems worse. Now somebody teaches me about 'go get'. Great! package whatever/thing/frob: unrecognized import path "whatever/thing/frob" (import path does not begin with hostname) (To be clear, I now can build all the golang code I want. This post is more indicative of my experience getting started a few years ago. In my opinion, GOPATH is a terrible design decision.)