minimum-version checks on user-supplied parameters make packaging a real pain

[mgorny]

Currently, scikit-build-core performs checks for deprecated options based on minimum-version. This is really painful for packagers who would like to use a single recipe across all packages. For example, in Gentoo we want to always use verbose builds. So we passed cmake.verbose=True — until we discovered it breaks some packages:

ERROR: Cannot set cmake.verbose if minimum-version is set to 0.10 or higher

So we switched to build.verbose=True instead. Except that now a fair number of previously working packages broke:

ERROR: Cannot set build.verbose if minimum-version is set to less than 0.10 (which is where it was introduced)

This a real pain now since we'd have to actually parse pyproject.toml in every package to determine which arguments to pass. Could you please provide weaker version checks on user-supplied options?

[henryiii]

We should disable these for strict-config=false (we don’t, but we should). I’d like to ignore these for config-settings and env vars, but checking where it came from could be a bit tricky.

You could set minimum-version=0.10 as a workaround for now.