-
-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2 branch #102
Comments
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. |
Being a junior Gopher, I'm interested in your point of view. |
@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 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). |
The
So it seems their perspective is to only save those in the git and not the whole vendor tree. |
Could you move the master branch to a v2 branch in order to be compatible with gopkg.in and glide ?
The text was updated successfully, but these errors were encountered: