-
Notifications
You must be signed in to change notification settings - Fork 455
Git-ignoring the vendor/ directory #474
Comments
When a repo is git pushed to remote that has no source, how will that remote build the source w/o hitting the network? |
If you are looking for that feature, please see govendor. PS: If you migrate to govendor, please don't use it's migrate command. I suggest instead doing: $ godep restore
$ rm -rf Godeps vendor
$ govendor init
$ govendor add +ex |
Your point is fair, but I think that git-ignoring Edit: I just dug deeper into this and saw #123 and #131 along with the proposal to remove such feature. |
@cleung2010 |
I see. I was thinking maybe |
@cleung2010 Great! FWIW: My recommendation would be govendor. |
Readings: https://github.com/tools/gode http://jbeckwith.com/2015/05/29/dependency-management-go/ tools/godep#474 (should have gone for govendor?)
I am not all too familiar with the inner-workings of dependency resolution for Go, so I wanted to know the reason behind the need to (git) include
vendor/
in a Go project. Ifgo restore
would perform the vendoring before installing the packages in$GOPATH
I think there would be no need to commit dependency sources into the project.On
npm
, for instance, you would commit thepackage.json
which has references (among other things) to all the dependencies that the package needs, but you don't commitnode_pacakges
which is what contains the source.npm install
on the project would do the job of fetching all the dependencies. I was hoping for something similar ongodep
, which would make projects much lighter.The text was updated successfully, but these errors were encountered: