Text of stackoverflow.com › posts › 72115282 › revisions as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Revisions to What is "vendoring"? - Stack Overflow

Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives Return to Answer Post Timeline attribution to defunkt Source Link edited May 4, 2022 at 15:19 Tobu edited May 4, 2022 at 15:19 Tobu 25.6k reputation score 25641 4 4 gold badges 96 96 silver badges 100 100 bronze badges As far as I know the term comes from Ruby on Rails. It describes a convention to keep a snapshot of the full set of dependencies in source control, in directories that contain package name and version number.

The earliest occurrence of vendor as a verb I found is the vendor everything post on err the blog (2007 , a bit before the author co-founded GitHub ). That post explains the motivation and how to add dependencies. As far as I understand the code and commands, there was no special tool support for calling the directory vendor at that time (patches and code snippets were floating around). The err blog post links to earlier ones with the same convention, like this fairly minimal way to add vendor subdirectories to the Rails import path (2006).

Earlier articles referenced from the err blog, like this one (2005), seemed to use the lib directory, which didn't make the distinction between own code and untouched snapshots of dependencies. The goal of vendoring is more reproducibility, better deployment, the kind of things people currently use containers for; as well as better transparency through source control. Other languages seem to have picked up the concept as is; one related concept is lockfiles, which define the same set of dependencies in a more compact form, involving hashes and remote package repositories.

Lockfiles can be used to recreate the vendor directory and detect any alterations. The lockfile concept may have come from the Ruby gems community, but don't quote me on that. The solution we’ve come up with is to throw every Ruby dependency in vendor . Everything. Savvy? Everyone is always on the same page: we don’t have to worry about who has what version of which gem. (we know) We don’t have to worry about getting everyone to update a gem. (we just do it once) We don’t have to worry about breaking the build with our libraries. […] The goal here is simple: always get everyone, especially your production environment, on the same page.

You don’t want to guess at which gems everyone does and does not have. Right. There’s another point lurking subtlety in the background: once all your gems are under version control, you can (probably) get your app up and running at any point of its existence without fuss. You can also see, quite easily, which versions of what gems you were using when. A real history. As far as I know the term comes from Ruby on Rails.

It describes a convention to keep a snapshot of the full set of dependencies in source control, in directories that contain package name and version number. The earliest occurrence of vendor as a verb I found is the vendor everything post on err the blog (2007). That post explains the motivation and how to add dependencies. As far as I understand the code and commands, there was no special tool support for calling the directory vendor at that time (patches and code snippets were floating around).

The err blog post links to earlier ones with the same convention, like this fairly minimal way to add vendor subdirectories to the Rails import path (2006). Earlier articles referenced from the err blog, like this one (2005), seemed to use the lib directory, which didn't make the distinction between own code and untouched snapshots of dependencies. The goal of vendoring is more reproducibility, better deployment, the kind of things people currently use containers for; as well as better transparency through source control.

Other languages seem to have picked up the concept as is; one related concept is lockfiles, which define the same set of dependencies in a more compact form, involving hashes and remote package repositories. Lockfiles can be used to recreate the vendor directory and detect any alterations. The lockfile concept may have come from the Ruby gems community, but don't quote me on that. The solution we’ve come up with is to throw every Ruby dependency in vendor .

Everything. Savvy? Everyone is always on the same page: we don’t have to worry about who has what version of which gem. (we know) We don’t have to worry about getting everyone to update a gem. (we just do it once) We don’t have to worry about breaking the build with our libraries. […] The goal here is simple: always get everyone, especially your production environment, on the same page. You don’t want to guess at which gems everyone does and does not have.

Right. There’s another point lurking subtlety in the background: once all your gems are under version control, you can (probably) get your app up and running at any point of its existence without fuss. You can also see, quite easily, which versions of what gems you were using when. A real history. As far as I know the term comes from Ruby on Rails. It describes a convention to keep a snapshot of the full set of dependencies in source control, in directories that contain package name and version number.

The earliest occurrence of vendor as a verb I found is the vendor everything post on err the blog (2007 , a bit before the author co-founded GitHub ). That post explains the motivation and how to add dependencies. As far as I understand the code and commands, there was no special tool support for calling the directory vendor at that time (patches and code snippets were floating around). The err blog post links to earlier ones with the same convention, like this fairly minimal way to add vendor subdirectories to the Rails import path (2006).

Earlier articles referenced from the err blog, like this one (2005), seemed to use the lib directory, which didn't make the distinction between own code and untouched snapshots of dependencies. The goal of vendoring is more reproducibility, better deployment, the kind of things people currently use containers for; as well as better transparency through source control. Other languages seem to have picked up the concept as is; one related concept is lockfiles, which define the same set of dependencies in a more compact form, involving hashes and remote package repositories.

Lockfiles can be used to recreate the vendor directory and detect any alterations. The lockfile concept may have come from the Ruby gems community, but don't quote me on that. The solution we’ve come up with is to throw every Ruby dependency in vendor . Everything. Savvy? Everyone is always on the same page: we don’t have to worry about who has what version of which gem. (we know) We don’t have to worry about getting everyone to update a gem. (we just do it once) We don’t have to worry about breaking the build with our libraries. […] The goal here is simple: always get everyone, especially your production environment, on the same page.

You don’t want to guess at which gems everyone does and does not have. Right. There’s another point lurking subtlety in the background: once all your gems are under version control, you can (probably) get your app up and running at any point of its existence without fuss. You can also see, quite easily, which versions of what gems you were using when. A real history. wording Source Link edited May 4, 2022 at 15:11 Tobu edited May 4, 2022 at 15:11 Tobu 25.6k reputation score 25641 4 4 gold badges 96 96 silver badges 100 100 bronze badges As far as I know the term comes from Ruby on Rails.

It describes a convention to keep a snapshot of the full set of dependencies in source control, in directories that contain package name and version number. The earliest occurrence of vendor as a verb I found is the vendor everything post on err the blog (2007). That post explains the motivation and how to add dependencies. As far as I understand the code and

The rest of this page is on the live site.