3 ms·
> Everyone I actually know agrees that submodules are basically never the right solution or a pleasant solution. I generally prefer submodules to other solutio
by jcelerier 6y ago
> Everyone I actually know agrees that submodules are basically never the right solution or a pleasant solution.
I generally prefer submodules to other solutions as I tend to fix / change a lot of stuff in the libraries that I'm using
- saurik 6y agoYeah: using submodules makes maintaining vendor patches (which, FWIW, I pretty much don't do and will move mountains to avoid... but like, I totally appreciate why people do them) really natural and easy. Like, you don't just want a copy of the code: you want to be able to participate in the development of the upstream code with the same level of tooling that they have, and submodules does that.
- steveklabnik 6y agoThe approach here would be to declare the dependency on the git repo directly. Vendoring is still going to copy the stuff you're building into your project, but you'd keep those patches in the repository of the dependency, not on your vendored copy.
- saurik 6y agoThe key thing here is being able to do it through multiple levels of dependency, for which I see someone else provided me an answer that is actionable! \o/