The case for Vendored Builds
summary
Argues that bundling every compiler, library and build system into the repo yields repeatable builds and simple onboarding, lets one perform rollbacks without hassle, and decouples development from local environments so CI is just clone-and-build. Draws from game-dev practice and warns about repository bloat and git’s poor handling of binaries, recommending Perforce or Plastic SCM for large assets and contrasting vendored builds with package managers like Conan.
AI-written summary · about
chapters (3)
related talks
03mWhy not Conan (part II)?
09mC++ Package Manager
32mBuilding and Maintaining Rust at Scale
29mPublishing High-Quality Crates
47mIt's all in the delivery
59mCase For a Standardized Package Description Format for External C++ Libraries
22mShipping a Solid Rust Crate
19m"Embracing Monorepo and LLM Evolution"