Henry Schreiner

What happens, out of curiosity, if you set `CMAKE_INSTALL_PREFIX` to `SKBUILD_DATA_DIR` inside the Python CMake files? Does the `cmake --install` command override this?

Not following everything, but a few quick comments: > Yep, the C++ cmake files already handle this. They have essentially No! You can't do this. The value of `SYSTEM_USES_LIB64` comes...

It cannot be triggered by scikit-build-core, because we don't use setuptools. Ninja still uses scikit-build classic, there hasn't been a release since we moved it to scikit-build-core. Also pybind11 uses...

Ah, sorry, yes the xfail approach is preferred.

I'm thinking of pybind11 and nanobind, specifically, which ship a `*Config.cmake` file. They place it in the correct location so `cmake.prefix` isn't necessary, scikit-build-core will find it without an entry...

macOS doesn't have gnutar as an option in it's bsdtar. ``` tar(bsdtar): manipulate archive files First option must be a mode specifier: -c Create -r Add/Replace -t List -u Update...

``` Copying project into container... + mkdir -p /project tar: gnutar: Invalid archive format Try `tar --help' or `tar --usage' for more information. tar: Write error ✕ 0.78s ```

> it depends on `VSCMD_ARG_TGT_ARCH` environment variable That's not in a release yet, correct? It will be in the next one (soon).

I'd probably like to wait till 1.0 (which is probably ~3 months away); dropping a Python version means we have LTS support on the last 3.7 one. Maybe sooner, if...

FWIW, 3.7 is the third most popular Python version [downloading](https://pypistats.org/packages/scikit-build-core) scikit-build-core. 3.11 dominates by a _ton_, though - factor of 10. Something must be up with that, you don't see...