18 ms·
To vendor a dependency is to store a copy of all the source code you're trying to use inside your project itself. That way, when you compile your project, you a
by sudhirj 11y ago
To vendor a dependency is to store a copy of all the source code you're trying to use inside your project itself. That way, when you compile your project, you also compile the code it depends on.
Updating code you depend on is a semi-manual process - you choose to copy the latest version of the code you depend on into your project again.
This is contrast to stacks like Java, where I can give you a pre-compiled JAR file that you can link your code to.
- fpoling 11y agoI have found that using git-subrepo is a great help with vendoring as single git subrepo pull --all is enough to update all dependencies.
- fludlight 11y agoIs this different from statically linked libraries (as opposed to dynamically linked)?
- NateDad 11y agoThis is about code, not libraries. Vendoring the code means copying it into your own repo... that way you're guaranteed that everyone who builds your project is building the exact same code, and if one of the third party repos disappears, your project doesn't all of a sudden fail to compile.