3 ms·
Vendoring packages doesn't mean vendoring in git. Vendoring in git is a terrible idea (which for some absurd reason the golang community has decided isn't...).
by scrollaway 9y ago
Vendoring packages doesn't mean vendoring in git. Vendoring in git is a terrible idea (which for some absurd reason the golang community has decided isn't...). It pollutes your tree, your history, your blames, your searches, makes your git repository massive, etc etc.
Node would be even worse.
- the_duke 9y agoWell, Go doesn't have a package system and no good external tool to circumvent it. So the choice is either maintain a fork of every dependency or vendor them, and vendoring is considerably less painful imo. (I'm not saying it's a good solution, mind you)
- icebraining 9y agoWe vendor in git by having a master repo, inside of which you have a submodule for our app and others for the dependencies. That way we can track and keep them in sync without having the problems you described.
- scrollaway 9y agoYeah submodules are a nice way to do git-based vendoring. I don't understand why the golang community didn't go that route.