> Too many C++ tools couple package management and build Conan does this too. If I follow the instructions to integrate cmake with conan, I would write somethi

> Too many C++ tools couple package management and build Conan does this too. If I follow the instructions to integrate cmake with conan, I would write something like this: include(${CMAKE_BINARY_DIR}/conanbuildinfo.cmake) conan_basic_setup(TARGETS) add_executable(timer timer.cpp) target_link_libraries(timer CONAN_PKG::Poco) Which now couples my build with conan. If the user would like to pull down the dependencies without conan(ie using apt-get or manually installing them), the cmake build script will not work. Package managers like cget[1] or conda[2] does not couple the build with the package manager. Cget is also serverless which is nice as it can install dependencies from anywhere(even directly from github with `cget install jgm/cmark`), however, you need to setup your own server hosting if you want to install binaries. [1]:http://cget.readthedocs.io/en/latest/ http://cget.readthedocs.io/en/latest/ [2]:https://conda.io/docs/intro.html https://conda.io/docs/intro.html