Goop – Dependency Manager for Go

https://github.com/nitrous-io/goop

by alixaxel • 12 years ago

71 43 12 years ago

github.com

aosmith2• 12 years ago

I've been doing basically the same thing by creating src/ and pkg/ directories and using this alias:

go='GOPATH=`pwd`:$GOPATH go'

dengnan• 12 years ago

In this case, try to run a `go get`, it will install everything into your current directory's bin/ directory.

aosmith2• 12 years ago

go get still works but it uses the src/ ... AFAIK there's no bin/ with go...

dz0ny• 12 years ago

set -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.

rem7• 12 years ago

I also setup my path per project. And vendor all my deps under _vendor And for getting libraries instead of doing go get I use git subtrees like so:

git subtree add --prefix _vendor/src/github.com/crowdmob/goamz https://github.com/crowdmob/goamz.git master --squash

jameskilton• 12 years ago

What does this offer that godep doesn't?

shurcooL2• 12 years ago

Or, in what ways does the design philosophy here differ enough to warrant a separate project instead of making PRs to godep?

raingrove3• 12 years ago

Because we love choice?

Godep wants you to touch your GOPATH. For example, `godep save` saves revisions of packages currently installed in your GOPATH and `godep restore` downloads packages into your current GOPATH. If you don't want to pollute global GOPATH, you will have to change it. This works for some people, doesn't for others.

Goop doesn't want you to worry about GOPATH. Goop also encourages you to explicitly state which packages you are using in the Goopfile, rather than "capturing" what is already in use.

leccine3• 12 years ago

Goop 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.

macrael2• 12 years ago

What does Erlang do?

leccine3• 12 years ago

Gets you downvotes on HN.

alecthomas• 12 years ago

Config file is nicer than godep; easily generated with a bit of shell. Quite nice.

imslavko• 12 years ago

It 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.

raingrove3• 12 years ago

You are right. Unfortunately, constraints resolution isn't something that can be implemented in a practical manner until there is a standard versioning scheme (there isn't much you can do with git hashes) and a standard dependency manifest file that every go project adopts.

Goop has `Goopfile.lock` and `goop exec`, inspired by Bundler's `Gemfile.lock` and `bundle exec`.

grey-area5• 12 years ago

until there is a standard versioning scheme (there isn't much you can do with git hashes)

Couldn't you use tags for versioning? Often people use tag v1.1.1 etc?

munificent• 12 years ago

From the looks of it, it just has a lockfile. None of the version resolution that makes bundler interesting.

vmiroshnikov• 12 years ago

If someone looks for an alternative, consider this kit:

https://github.com/pote/gvp - virtualenv in go's world

https://github.com/pote/gpm - pip in go's world

dkulchenko• 12 years ago

Looks fantastic, thanks for this!

sswaner• 12 years ago

Hope Gwyneth Paltrow doesn't get upset about the name. http://www.goop.com

dead10ck2• 12 years ago

I'm curious why so many of these Go dependency managers are popping up. Doesn't go get download all dependencies automatically? Why are these third-party dependency managers necessary?

collinvandyck76• 12 years ago

Because 'go get' does not allow you to point to a particular revision. It downloads the latest / HEAD commit for that dependency and sticks it into ${GOPATH}. These dependency managers are all aiming to fix that problem, and some of them, I believe, transitively.

dead10ck2• 12 years ago

Why would you want to use an older version of a package? Just to ensure compatibility by using a version known to work?

jzelinskie2• 12 years ago

For git (and probably others) It actually looks for a "go1" tag, and if not there it uses the head of master.

I honestly don't care for all these version managers. If I didn't trust the author of whatever library I'm pulling in to keep their API stable, then I wouldn't use that library or I'd preemptively fork. This is actually a language convention and if more people were familiar with it, there would be even less issues (though I haven't ever had any personally). If you're interested in helping the community familiarize themselves with Go's language conventions, I made a package[0] that developers should read after going through the Go Tour. It's meant to teach best practices and conventions for library design in Go.

[0] https://github.com/jzelinskie/conventions

kylered• 12 years ago

In case anyone is interested, we open sourced this one about a year ago: https://github.com/VividCortex/johnny-deps

Goop – Dependency Manager for Go

Related Stories