Why not Conan?
summary
Argues Conan is not a C++-only manager because it accepts C packages and is not written in C++, and criticizes bundled packages like OpenSSL that feel irrelevant to some C++ projects. Calls out the ecosystem where anyone can upload packages, so searching for Boost yields many competing recipes and confusion. Notes the project's small footprint with ~600 GitHub stars, ~60 forks, ~23 contributors, and contrasts that with reliance on system package managers and language-specific ecosystems.
AI-written summary · about
chapters (6)
- 0:00Why not Conan? 5 reasons not to use conan package manager
- 0:15Because it is not a C++ package manager
- 0:40Because it is not written in C++
- 0:59Because it is not needed, I already have apt, yum, nuget, brew...
- 1:24Because there is not a single reference Boost, Poco, Zlib, ... package
- 2:04Because it is not mainstream
related talks
03mWhy Conan? 5 reasons to use Conan package manager
01h 01mGit, CMake, Conan - How to ship and reuse our C++ projects
01h 01mPackage management in C++
01h 11mThe State of Package Management in C++
22mBuilding Portable C++ Packages: The Bliss of Unification
01h 08m“Faster Delivery of Large C/C++ Projects with..."
01h 20mContinuous Integration for Large Scale C/C++ Projects With Conan2
01h 12mC++ Package Manager - C++ Dependencies Don't Have To Be Painful!