Cristian Le

> My guess is "clobbered" means that when it computes the wheel tag it doesn't look up CMAKE_OSX_DEPLOYMENT_TARGET but just sets the current macOS version as the tag. Ok, so...

The issue is that right now `scikit-build-core` only reads `MACOSX_DEPLOYMENT_TARGET` environment variable for figuring out what the `.whl` file and compiled python module names should be. Indeed the action for...

Just to emphasise, we are not dependent on `cibuildwheel` workflow and we want to support as many workflows as possible and try to work with the developers there as closely...

> What's wrong with passing `-C`? I'd like to focus on things that can't be done, not adding a second way to do things that are already supported. Is the...

Sounds reasonable, PR welcome :). Ideally we keep the older supported/available versions which should be the `pyp-3.9` ones. A new `pypy-3.10` for macos might need to be added as the...

What would be a nice interface is to try and query the service for what topics it provides and provide a drop-down selection for them. Otherwise it is too magical...

Great idea! To flesh out this a bit more, how should the project define the `CMakePackageConfigHelpers` calls to support standard and wheel install paths, e.g. `INTALL_DESTINATION`. Probably it's more an...

> Ahh, but a module path could resolve to several physical paths. But I think we could just then pick the one with the config file in it? Shouldn't be...

> > We've been supporting directly specifying the directory and not requiring an entry point function. > > How? How does the consuming project find the directly-specified directory? I guess...

Hmm, also occurs to me, how would one disable the preference of the entry_points? For `CMAKE_PREFIX_PATH` it is somewhat doable if we make sure to append to the existing value,...