v2 branch

[Scapal]

Could you move the master branch to a v2 branch in order to be compatible with gopkg.in and glide ?

[pkieltyka]

I'm not a fan of either gopkg.in or glide. I prefer just normal vendoring (ie. govendor).

I can make a v2 branch that mirrors master if it helps others though. What is required? (can you give me the debrief before I say yes/no), thanks.

[Scapal]

Being a junior Gopher, I'm interested in your point of view.
Does using govendor mean that you put the vendor tree in your Git as well?
The purpose of a glide.lockis to avoid that.

[pkieltyka]

@Scapal a group that is part core and part community is working on a dependency management tool -- here is the draft: https://docs.google.com/document/d/1qnmjwfMmvSCDaY4jxPmLAccaaUI5FfySNE90gB0pTKQ/edit

since Go 1.7, the go cli will recognize packages in a ./vendor folder first then search $GOPATH for depedencies. Look up "go vendoring". The missing part today which the draft above covers and tools like glide and govendor implement is actually fetching and managing the files in ./vendor/

a good approach (like govendor does), is store the lock file in ./vendor/vendor.json

and yes absolutely commit your vendor tree to git. it's actually a very nice experience.

govendor is great, except the cli is kind of awkward because its so powerful. hopefully the guys working on the dep tool above will achieve something very smooth (im confident they will).

[Scapal]

The dep tool in the draft mention:

Lockfile and Manifest are two files. Located in the project root.

So it seems their perspective is to only save those in the git and not the whole vendor tree.
It is the same approach used by Composer for PHP and Glide.
Wouldn't it be awkward for an open-source project to include the full dependencies in vendor?