Thanks. It looks like at least the third bullet has been reconsidered, based on this announcement. But I think the front matter on that section gives (at least

Thanks. It looks like at least the third bullet has been reconsidered, based on this announcement. But I think the front matter on that section gives (at least for what I'm after) a pretty good start on an answer to my question. They aim to version all libraries together as a platform (like, say, homebrew or yum+rpm). Where Conan aims to behave a little more like what I'd term "pypi for C++". That is, if I'm reading this correctly, and I'm not yet certain that I am. One thing that I want to do, and it's clear to me how I'd do it with conan (or pip) but not yet clear to me how I'd do it with vcpkg, is have a version of a package that's available in a public repository also be available in my internal repository with some added private patches, and have my version "win" for my projects. Our recurring need for this is when we're building out patches that we want to have incorporated upstream but aren't ready to do that yet for one of many reasons.