<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <blockquote type="cite" cite="mid:boris.20181211144635@codesynthesis.com"> <pre class="moz-quote-pre" wrap="">IMO, build2 is actually quite different from cmake/conan/vcpkg. Maybe a better description would be: "build2 is a next-generation, Cargo-like integrated build system and package manager for C++." </pre> </blockquote> Personally for me build2 is package (dependency) manager at first. It also build system, but this is less important. C++ people are know what is conan and vcpkg, so I mentioned those projects. But as You wish (fixed build2 description almost literally but saved conan and vcpkg mentioning). Available here <a class="moz-txt-link-freetext" href="https://masterspline.gitlab.io/build2-linux-packages/">https://masterspline.gitlab.io/build2-linux-packages/</a> and <a class="moz-txt-link-freetext" href="https://gitlab.com/masterspline/build2-linux-packages">https://gitlab.com/masterspline/build2-linux-packages</a> I still want at least "unofficial deb/rpm packages repository" status and link somewhere from build2.org (FAQ, installation page, anythin googlabe). In my defense I created rpm and deb packages, Installation HowTo, HTTPS Repository. This do not looks like shallow way (несерьезный, поверхностный подход). Official Debian packages for build2 not an easy solution (I thought about this<span style="color: rgb(128, 128, 128); font-family: "Times New Roman", Times, serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(219, 219, 219); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">). Because build includes except libbutil, libbpkg also libpkgconf, libsqlite3, libodb and all this packages MUST (as I know) be in debian system. But buil2-toolchain will want fresh versions and debian policy have it's own opinion when and how to upgrade library version in system. There is conflict between Debian policy and build2-toolchain needs, So Imade /usr/lib/build2 directory with shared libs and I use RPATH (do not think this allowed for official debian package). Solution with static libraries also not perfect. So inclusion build2-toolchain in official repository require some build2 stabilization, some time and some more work. But Boris If You really want build2 be used it need to be as easy to install and use as possible. My packages are just one step in this direction. Alex </body> </html>