Re:Code.google.com was shut down, Go packaging is broken
by nothrabannosir on Tuesday January 26, 2016 @09:40AM
(#10973553)
Vendoring through tarball dumps of GOPATH I can understand, but how do you deal with the dependencies of your dependencies when vendoring through forking?
[ Parent
| on HN ]
Re:Code.google.com was shut down, Go packaging is broken
by voidlogic on Tuesday January 26, 2016 @10:37AM
(#10973897)
Of our 40 or so external dependencies (huge project), only a handful themselves have dependencies we needed to also vendor. Its sounds painful, but in practice it hasn't been. We actually stopped using godep, we were getting no reward for the hassle and added complexity.
Unless there is a bug, or new feature we needed, we often just update this stuff when we update the Go release we are using.
My thoughts; KISS until more complexity is actually needed.
Re:Code.google.com was shut down, Go packaging is broken
by nothrabannosir on Tuesday January 26, 2016 @10:56AM
(#10974012)
> My thoughts; KISS until more complexity is actually needed.
Well, isn't that exactly what this artice is about…?
Re:Code.google.com was shut down, Go packaging is broken
by ihsw on Tuesday January 26, 2016 @10:37AM
(#10973890)
It does kick the can down the road, but it kicks it pretty far.
I'm not the parent but your question is completely valid -- trying to get dependencies of dependencies sends us down a very deep rabbit hole.
This is usually where dynamic linking and shrinkwrapping[1]/vendoring[2] start entering serious discussions.
[1] http://blog.goguardian.com/nerds/shrinkwrap-not-just-for-mur...
Re:Code.google.com was shut down, Go packaging is broken
by a3n on Tuesday January 26, 2016 @11:04AM
(#10974068)
Wouldn't you just follow that through to the leaves?