3 ms·
> Still have to deal with GOPATH Once, when you install Go. Then for each project, put your stuff where you want and symlink from $GOPATH to where it is. Once
by rakoo 12y ago
> Still have to deal with GOPATH
Once, when you install Go.
Then for each project, put your stuff where you want and symlink from $GOPATH to where it is. Once per project.
There really is minimum hassle to integrate the recommended flow.
- NateDad 12y agonote that symlinking is not actually the recommended flow ;) Just put everything in gopath.... I even put non-go code in my gopath... it's just a nice way to organize - by the VCS url.
- kmontrose 12y agoYou also install runtimes once for other languages. GOPATH isn't awful, but it's something more than "just source" as claimed in the article; which is my point. Go is simple, but not as simple as claimed.