How do Glide managed dependencies work with a build?

Question

I am using Go 1.7 and trying out Glide. The part I'm not getting is, Glide creates a vendor directory at $GOPATH/vendor. But when go builds it is looking for a vendor directory at $GOPATH/src/github.com/vendor/.../...

So I'm missing the part that happens between installing/updating dependencies and making them available to my program during a build.

Answer 1

Adding the answer for the next poor soul that comes along.

If you're coming from the Java world, and you are used to the src directory being at the root of your project... Go says you are wrong. As the commenter indicated, your project path is $GOPATH/src/[github.com]/username/projectname and that is where you should do your "glide init".

That will create the glide.yaml file in the correct spot so "glide install" will create the vendor directory at $GOPATH/src/githost/username/projectname/vendor and then your go builds will work as expected.

Hopefully this will clear it up for other folks who might have similar questions.