Kai Pastor

> I don't think that vcpkg has a way to know which is the current python executable. For ports depending on a particular version of python, a dependency on `python3`...

That's probably a left-over TODO from devendoring the deps. Inspect what the original file does, and how to achieve the effect. Maybe it is obsolete, maybe it needs a different...

Do not put vcpkg into /opt. CMake applies special tricks for this prefix.

Many packages put headers into subdirs of `include`, and they export the location via CMake or pkg-config. That's fine. msbuild is unable to use this exported information, and vcpkg doesn't...

Needs #35973.

> Upstream recommends setting `/tmp` What I read is: Upstream recommends using meson and setting `session_socket_dir`.

Anyways, we already identified the option, and someone has to form a valid PR. This one isn't.

The CI issue is fixed...

Did you verify that it is okay to remove the DLLs? Either they are plugins, or they come with an import lib.

IMO the primary message is not "port bug", but "CI broken" because `vcpkg ci` is broken. And it is not solved. ~~~ -- Performing post-build validation warning: File /Users/vcpkg/Data/installed/arm64-osx/lib/libMath.a was...