gpm

Seems like the author is suggesting something very similar to what [gpm][1][2] provides. I use gpm for a few projects, along with a makefile that creates a GOPATH at $(pwd)/_build, and it works fairly well. [1]: http://java.dzone.com/articles/why-gpm-right-go-package [2]: https://github.com/pote/gpm

I don't believe so. Your options are still pretty much: (a) vendoring with something like godep[1], or (b) point in time scm fetching with something like gpm[2]. [1]: https://github.com/tools/godep [2]: https://github.com/pote/gpm

I use godep for a couple of projects. It works pretty well. Sometimes the path rewriting feels a bit dirty though, and can make adding new imports/dependencies a bit of a chore. For a couple of projects I was using godep with the `-copy=false` mechanism, and was sad to see it go. As a replacement for that functionality, I have had good luck with gpm[1]. I just put the build script in a build or tools dir (the script is quite small), and make it part of a make build invocation, to remove the external requirement. [1]: https://github.com/pote/gpm

Pote's GVP/GPM works really well here. It's such a small system to learn and use, but does everything you could ever need when versioning godeps: https://github.com/pote/gpm && https://github.com/pote/gvp

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

You can use gvp (https://github.com/pote/gvp) to isolate your workspaces (GOPATHs, really) for each of your projects, you can then include your dependencies in your project's repo or have a Godeps file specifying versioning which you can use with gpm (https://github.com/pote/gpm). Hope you find it useful! :)

I also find gpm to be quite nice and resemble npm. (https://github.com/pote/gpm) yeah, it's sad that go doesn't come with better dep and workspace built-in

Have you tried GPM? https://github.com/pote/gpm