3 ms·

I still worry that devs who say, "oh crap we can't build because of this library" are doing something wrong. I'm curious why I must depend on complexities like

I still worry that devs who say, "oh crap we can't build because of this library" are doing something wrong. I'm curious why I must depend on complexities like this or godeps to write effective go either by myself or in a team. Can't you just take a snapshot of the source including third party libs and keep it somewhere safe? Edit: stablelibs is an inviting idea if you believe you must vendor, and plenty of people do believe that.

Zikes 12y ago
I think vendoring is being officially promoted, with a concrete workflow/plan in the works to be announced later.
- dchest 12y ago
  Yes, here's a post by bradfitz https://groups.google.com/d/msg/golang-dev/nMWoEAG55v8/iJGgur7W_SEJ https://groups.google.com/d/msg/golang-dev/nMWoEAG55v8/iJGgu...
dchest 12y ago
Can't you just take a snapshot of the source including third party libs and keep it somewhere safe? That's what vendoring is for — freezing your dependency on some version. What StableLib provides is a guarantee that the API of package remains stable, but also that all the latest major/security bugs are always fixed (by backporting them). Also, that you're always notified about any critical/security fixes. Of course, you can also do vendoring with StableLib-provided packages, and we plan to make it easy via the command-line tool.