On Tue, Jul 5, 2016 at 10:17 AM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > AFAIK, vendoring explicitly implements an all-or-nothing approach: > you're supposed to resolve transitive dependencies yourself, and vendor > them all.
That's my understanding too, but it seems foolish to vendor a version of a library that's in the same repo (eg. using the "root of the repo is the library, and a cmd/ directory has a few commands are thin wrappers around the library" project structure that's so common). Since keeping up to date with the library that actually implements the commands is part of the contract, vendoring it seems like a bad idea. —Sam -- Sam Whited pub 4096R/54083AE104EA7AD3 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
