The need for a package manager interface

on YouTube ↗08m

" summary

C++ lacks a standard interface between package managers and build systems so projects avoid reuse; dozens of build systems and thousands of existing projects make ripping and replacing impractical. The claim: define a simple protocol so a package manager like Conan (bin-crafters counts ~200 packages vs ~20 on Conan master) queries the build system, reports missing dependencies, installs what’s missing, then invokes the build. Proven approach: wrapper package managers plus per-package scripts work but scale poorly; a lightweight opt-in protocol could fix migration pain.

AI-written summary · about

" chapters (4)

1. 0:00The problem with C++
2. 2:20Build systems and packages
3. 3:52Migration paths and solutions
4. 5:26The need for a standard

" related talks

• 59mCase For a Standardized Package Description Format for External C++ LibrariesLuis Caro Campos · CppCon 2022
• 09mC++ Package ManagerBoris Kolpackov · CppCon 2014
• 01h 04mWhat's New in Conan 2.0 C/C++ Package ManagerDiego Rodriguez-Losada · CppCon 2022
• 03mWhy not Conan (part II)?Diego Rodriguez-Lopez · CppCon 2017
• 01h 07mC++20 Modules: The Packaging and Binary Redistribution StoryLuis Caro Campos · CppCon 2023
• 01h 02mCMake and the Future of C++Julien Jomier · Meeting C++ 2021
• 01h 01mClean CMake for C++ (library) developersKerstin Keller · Meeting C++ 2024
• 05mC++ Modules and Packages: Making Dreams Come TrueBoris Kolpackov · CppCon 2017