Why not Conan (part III)?
summary
Five quick claims: Conan feels too complex and nondeclarative, arguing for scripting hacks instead of clear recipes; company policy favoring source builds over binaries is named as a virtue; GitHub activity doubled and number of companies tripled in months, with Conan now second‑most active on Slack; developers still run pip install monthly so they “don’t eat their own dog food”; uploader cites one million dollars in August as a headline metric.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:09Why not conan (part III)? 5 (more) reasons not to use Conan package manager
- 0:41It is not declarative
- 1:21It allows reusing binaries
- 2:01They are not eating their own dog food
- 2:27It is not standard (ISO)
related talks
57mUsing Conan in a real-world complex project
28mConan, a C and C++ package manager for developers
01h 20mContinuous Integration for Large Scale C/C++ Projects With Conan2
01h 08m“Faster Delivery of Large C/C++ Projects with..."
01h 04mCMake and Conan: past, present and future
44mWhats new in Conan 2.0
06mLightning Talk: DevSecOps for C++? Keep Calm and use Conan
50mModern DevOps in C and C++