Goop – Dependency Manager for Go
github.com
Goop – Dependency Manager for Go
1–10 of 46 posts
Re: Goop – Dependency Manager for Go
#2I've been doing basically the same thing by creating src/ and pkg/ directories and using this alias:
go='GOPATH=`pwd`:$GOPATH go'
Re: Goop – Dependency Manager for Go
#3set -x GOPATH (PWD)/.vendor
set -x GOBIN (PWD)/.vendor/bin
And committing stuff in git when it matters.
gvm is also nice for testing stuff with different versions of go.
Re: Goop – Dependency Manager for Go
#4What does this offer that godep doesn't?
Re: Goop – Dependency Manager for Go
#5Goop for teh rescue! The only trouble I had with go is the dependency handling. I wish people realize how Erlang's way of dealing with this is superior.
Re: Goop – Dependency Manager for Go
#6Goop for teh rescue! The only trouble I had with go is the dependency handling. I wish people realize how Erlang's way of dealing with this is superior.
What does Erlang do?
Re: Goop – Dependency Manager for Go
#7Config file is nicer than godep; easily generated with a bit of shell. Quite nice.
Re: Goop – Dependency Manager for Go
#8I've been doing basically the same thing by creating src/ and pkg/ directories and using this alias: go='GOPATH=`pwd`:$GOPATH go'
In this case, try to run a `go get`, it will install everything into your current directory's bin/ directory.
Re: Goop – Dependency Manager for Go
#9What does this offer that godep doesn't?
Or, in what ways does the design philosophy here differ enough to warrant a separate project instead of making PRs to godep?
Re: Goop – Dependency Manager for Go
#10It says it is inspired by Bundler but in what ways? I am curious as I didn't use much of neither bundler nor goop but I have heard the constraints resolution lays in the heart of bundler.