Trying to be constructive, I would say this needs to zoom out a few layers and make a case for what concepts it is trying to address.<p>The primary means to distribute open source software is via source code. Automagical technologies to assemble all the source code for a dependency tree, and&#x2F;or automagical technologies to fetch precompiled dependency trees with curated options, versions, component granularities, etc are extremely non-trivial problems. To date the only examples of this done with a measure of effectiveness are actually entire operating system distributions backed by software like apt, yum, pkg-src, etc.<p>Primarily because of the total failure in this regard of windows and osx, individual languages themselves starting advancing ecosystem centric dependency management with files retrievable from servers hosted on line. At best, this style strategy solves some of the problems some of the time, and at worst breaks the ability to make things even work the old way - ie manual download, assembly, and compilation of source code dependency trees.<p>In the context of largely portable, interpreted code, this sort of thing is at plausible. In the context of native code with multi-dimensional matrices of OS&#x2F;Compiler&#x2F;libc&#x2F;versions&#x2F;flags&#x2F;phases of the moon, the notion of a repository of precompiled binaries to even enough cover &quot;common cases&quot; to be thought of as a language level feature.<p>In the case of source dependency management, exposing the information about where and how things are installed and reachable for use in the build environment of the foreground project is hard enough, and trying to be able to hold cross platform build recipes of some sort is literally the creation of yet another operating system. Take homebrew for example.<p>Perhaps some sort of unification wrapper over apt and pkg-config is a thought, but honestly can&#x27;t even guess what problems can be addressed with something like this.<p>In all seriousness the only cross platform solution maintaining build environments is to just host all builds on linux, use mingw64 and osxcross along with apt or yum + regular pkg-config, git, etc.<p>This looks like someone who thinks things like pip and gem make sense trying to overlay that paradigm to a broader scope. Or maybe I&#x27;m just too old to &quot;get it&quot;. Please clue me in?