My status with godeps: “It’s Complicated.”
For some background, godep is a go dependency management tool. Basically, at a very high level, godep culls all of the source code needed by your code out of your development environment, and into a virtual work-space within your code base. Why would you EVER want to keep all of your dependency code within your source tree?? Well, there are plenty of reasons.
- Reproducible builds - This can’t be understated. With all of your source code together, in one place, you can make the same exact product build regardless of build environment, dev workstation, etc.
- Version Pinning - YOU have control over what gets built into your application,
not your upstream dependency developer.
go getliterally gets the latest of the dependency when it is run for the first time, so you have no idea what is going into your product.
- Simplify builds - Your build system will thank you, as it doesn’t have to go get every dependency, every time you perform a build.
- Easier Auditing - You can make sure your dependency is what you expect it is.
All of these reason scream for the need for robust dependency management. Enter my fr-enemy godep.
I <3 godep. Dependency management in go proper doesn’t exist. Godeps fills that void by allowing for commit level version pinning. See Below:
Sweet! I have every revision of every package my project needs to build successfully, moreover I have the commit comment of said revision. This is very helpful on it’s own. But wait, there is more:
Godep saved ALL of the required source to easily rebuild what I have at this exact moment in space time. WOW. This is excellent. No more need to cull all of the source code during a build of the software anymore. I can actually audit all of this code, and have and hold these dependency artifacts for the rest of my days, and they will never break due to “what’s changed” again!
I >:@ godep. Updating godeps is a huge pita. Dependencies have dependencies, which have dependencies. This is a fact of life. Godep is smart enough to figure this out on a godep save, and godep update, but it relies heavily on go get to do the heavy lifting when doing an update… If only all your dependencies also used a dependency management system… Here are the steps you have to follow when you want to make an update to an existing package with godeps:
- go get -u
- godep update
- rinse, repeat, for every package you want to update.
Not kidding. If the dependencies of those packages you want to update have changed, or are no longer valid in your dev environment, you will have to go get -u them too, and update godeps with the above. Ouch.
See, Godep uses your machine’s $GOPATH to find all of the dependencies for your project. They assume, probably correctly, that the developer is always right and does his/her due diligence to make sure all of the packages on one’s gopath are correct, and working together in harmony. bwahahaha.
Some developers I know, (yes I am talking about you), would rather throw caution to the wind, and blow away the entire Godeps directory in the codebase, and perform a godep save to quickly deal with updates to dependencies. Since the dependencies are stored in your codebase, this makes for some VERY interesting commits, for sure, and much squabbling and frustration for devs. >;)
Hope this was helpful to anyone.