Once again switch to the newer scikit-build-core `build.verbose` option to fix compatibility with packages requiring the newer version, and let us stop patching ebuilds. Upstream fixed the behavior to allow using newer options in `config_settings`.
Bug: https://github.com/scikit-build/scikit-build-core/issues/912 Pull-Request: https://github.com/scikit-build/scikit-build-core/pull/1054 Signed-off-by: Michał Górny <[email protected]> --- eclass/distutils-r1.eclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/eclass/distutils-r1.eclass b/eclass/distutils-r1.eclass index c59bdce17581..e9826f4cf3df 100644 --- a/eclass/distutils-r1.eclass +++ b/eclass/distutils-r1.eclass @@ -292,7 +292,7 @@ _distutils_set_globals() { ;; scikit-build-core) bdep+=' - >=dev-python/scikit-build-core-0.10.7[${PYTHON_USEDEP}] + >=dev-python/scikit-build-core-0.11.5[${PYTHON_USEDEP}] ' ;; setuptools) @@ -1145,9 +1145,9 @@ distutils_pep517_install() { ninjaopts = shlex.split(os.environ["NINJAOPTS"]) print(json.dumps({ "build.tool-args": ninjaopts, + "build.verbose": True, "cmake.args": ";".join(sys.argv[1:]), "cmake.build-type": "${CMAKE_BUILD_TYPE}", - "cmake.verbose": True, "install.strip": False, })) EOF
