Re:Toward Go 2
by brango on Thursday July 13, 2017 @02:20PM
(#14763791)
There's no obvious way to separate personal work, from work work, from exploratory work, from any other way you want to categorise your source directories. You just have to chuck them all in the same root and hope you can remember what each project is for.
[ Parent
| on HN ]
Re:Toward Go 2
by zbobet2012 on Thursday July 13, 2017 @02:48PM
(#14764014)
Uhh, just keep separate gopaths? I keep a separate go path per project.
Re:Toward Go 2
by kevinmgranger on Thursday July 13, 2017 @02:59PM
(#14764119)
That is the reason why GOPATH is an environment variable: so you can change it easily, you own way.
Re:Toward Go 2
by artursapek on Thursday July 13, 2017 @02:48PM
(#14764012)
What? Manage it the way you'd manage any other environment variables, like AWS_SECRET_ACCESS_KEY. That's exactly what a bash environment is for.
You want to manage GOPATH as if it were a secret key!? Not ever storing it in repos, having weird dotfiles storing them locally, having to set up a keystore cluster like consul in production? Yuck.
Re:Toward Go 2
by artursapek on Thursday July 13, 2017 @10:37PM
(#14767010)
The point is it's a per-project config. And yeah, there's no reason to store "/home/artur/go" in my git repo - that wouldn't work for my coworkers whose names are not Artur.