[go-nuts] Re: Vendoring nested dependencies

2017-04-14 Thread mhhcbon
I use glide. Always flatten the vendor. In go, those two types are not identical,(Main depends on Bar@v1, Foo depends on Bar@v2) No matter what you do, as they exists in different directories, they can t be equals. hth On Thursday, April 13, 2017 at 9:47:21 PM UTC+2, JB wrote: > > Our team h

[go-nuts] Re: Vendoring nested dependencies

2017-04-13 Thread David Collier-Brown
As Russ Cox, a somewhat famous Gopher, noted, that's an NP-complete problem. You can pay in effort (several different interpretations of "flattening"), in compile speed(running a SAT solver) or you can fail (;-)) This won't help you, but the last three times we ran into this, we changed the pr

[go-nuts] Re: Vendoring nested dependencies

2017-04-13 Thread Ondřej Kupka
Doesn't flattening and using a service like gopkg.in solve this issue? Then you can have both flat structure and multiple versions of the same library since different versions of the same library appear as different packages since the import path is different. On Thursday, April 13, 2017 at 9:4