The Godep tool
I used Godep for a while. And it worked fine, but it was a hassle to use.
Godep created a Godeps.json file in a Godeps directory in the root of my project. Godep then created copies of all of my third-party packages into the Godeps directory at the root of my project. I typically checked those third-party packages into version control with the rest of my code.
Godep requires a number of steps that I find quirky. For example, to update a project's dependency, you will have to update it in your GOPATH via the go get -u github.com/another-thirdparty/package command, and then copy it from my $GOPATH to my project's Godeps directory via the godep save github.com/another-thirdparty/package command.
In my humble opinion, having to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access