News for hackers. Stuff that matters.

A comment on Looking at your program’s structure in Go 1.7. Parent comment

Re:Looking at your program’s structure in Go 1.7 by mseepgood on Tuesday August 16, 2016 @02:46AM (#12295928)
> But worst was probably the missing import path structure, i.e. "github.com/<company>/<repo>" that people simply just didn't get.

You obviously didn't vendor your dependencies in your project's vendor directory.

[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by CannisterFlux on Tuesday August 16, 2016 @03:19AM (#12296017)
I found vendor directories to be documented in a confusing way, so I'm not surprised.

https://golang.org/cmd/go/#hdr-Vendor_Directories

I think the example there is hard to follow. Perhaps with more standard package names, such as golang.org/x/net or a popular github.com package, instead of the made up foo, baz, quux and so on it would be easier to understand exactly what advantages vendoring gives you.

[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by twblalock on Tuesday August 16, 2016 @01:02PM (#12298836)
> You obviously didn't vendor your dependencies in your project's vendor directory.

You shouldn't have to!

A good dependency management system will produce reproducible builds via dependency versioning without any need to "vendor" anything.

[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by bigdubs on Tuesday August 16, 2016 @03:02AM (#12295980)
Vendoring doesn't work outside $GOPATH
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by mixedCase on Tuesday August 16, 2016 @11:58AM (#12298281)
Don't work outside $GOPATH. Set a temporary one if you want a completely isolated environment for one-off building purposes.
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by stouset on Tuesday August 16, 2016 @12:32PM (#12298558)
Then what's even the point in the first place?
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by mixedCase on Tuesday August 16, 2016 @01:22PM (#12298969)
Development. Which is why I said "for one-off builds".
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by icholy on Tuesday August 16, 2016 @11:19AM (#12298009)
Why is this the case?
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by Spiritus on Tuesday August 16, 2016 @03:08AM (#12295990)
It didn't have any external dependencies, only multiple packages.
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by 0xdeadbeefbabe on Tuesday August 16, 2016 @12:54PM (#12298770)
If you choose to vendor part of stdlib like http then boom diamond dependency problem approaches.
[ Parent | on HN ]
Re:Looking at your program’s structure in Go 1.7 by fpoling on Tuesday August 16, 2016 @02:50PM (#12299662)
Even if one vendors the external dependencies, the code that uses them must still be on GOPATH or the compiler would not find them. This is at least with go 1.6.
[ Parent | on HN ]