I've been using Gobrew: https://github.com/grobins2/gobrew
It would be nice to standardize this a bit. I'm sure other Go devs I work with use something different (I homerolled for awhile but I've been really pleased with Gobrew).
A simple virtualenv for Go
11–20 of 36 posts
Re: A simple virtualenv for Go
#12There's already a `goenv` https://github.com/wfarr/goenv, that I've been using for a bit. Also can do go version management.
Re: A simple virtualenv for Go
#13I was interested when I saw the project name, but this appears to be: mkdir -p pkg bin src export GOPATH="`pwd`" export PATH="$GOPATH/bin:$PATH" Only what I typed there is shorter and safer than the committed code. That's... simple, yes. https://github.com/ChuckHa/goenv/blob/master/goenv
How is yours safer?
Re: A simple virtualenv for Go
#14The approach we've taken at work is, each project has its own src/pkg/bin tree under the checked-in root, and we just set GOPATH. Simple and easy.
Re: A simple virtualenv for Go
#15The approach we've taken at work is, each project has its own src/pkg/bin tree under the checked-in root, and we just set GOPATH. Simple and easy.
This seems like a very reasonable approach. Thanks!
Re: A simple virtualenv for Go
#16There's already a `goenv` https://github.com/wfarr/goenv , that I've been using for a bit. Also can do go version management.
Thanks for pointing this out, I hadn't found it.
Re: A simple virtualenv for Go
#17I'm actually a little confused by go's global approach, which ultimately gives rise to the myriad of solutions listed in the comments here. Am I missing some go-centric way of thinking?
Re: A simple virtualenv for Go
#18This seems to copy a bad design decision from virtualenv. Please see https://gist.github.com/datagrok/2199506
I implemented the suggestions in this gist on a new branch here:
https://github.com/ChuckHa/goenv/tree/inve
I'm not sure I like it better though because it unsets $PS1 and other variables that get set in .bash_profile.
Re: A simple virtualenv for Go
#19I'm actually a little confused by go's global approach, which ultimately gives rise to the myriad of solutions listed in the comments here. Am I missing some go-centric way of thinking?
I think the documentation about go workspaces is just a simple approach and it's expected the community will eventually settle on a way to manage this in a non-global fashion.
I'm guessing everyone wants something slightly different and it would be pointless for Go to have One Way hence all the alternatives here.
Re: A simple virtualenv for Go
#20I'm actually a little confused by go's global approach, which ultimately gives rise to the myriad of solutions listed in the comments here. Am I missing some go-centric way of thinking?
I believe this is because they're in Google. For them, taking a VM instance would be more reasonable than multiplexing single machine into multiple virtualized environment.