Raise MAX_VERSION (currently 0.0.17)

[Flowdalic]

Emerging dev-python/pkgcraft-9999 fails with

pkgcraft C library 0.0.22 fails requirements <=0.0.17
 * ERROR: dev-python/pkgcraft-9999::gentoo failed (compile phase):
 *   Wheel build failed
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called src_compile
 *   environment, line 4306:  Called distutils-r1_src_compile
 *   environment, line 2000:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
 *   environment, line  665:  Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3861:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3403:  Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3401:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 1282:  Called distutils-r1_run_phase 'distutils-r1_python_compile'
 *   environment, line 1982:  Called distutils-r1_python_compile
 *   environment, line 1804:  Called distutils_pep517_install '/data-scratch/var-tmp/portage/dev-python/pkgcraft-9999/work/pkgcraft-9999-python3_12/install'
 *   environment, line 2332:  Called die
 * The specific snippet of code:
 *       local wheel=$("${cmd[@]}" 3>&1 1>&2 || die "Wheel build failed");

if a newer version than sys-apps/pkgcraft-tools-0.0.17 is installed.

Could MAX_VERSION be raised?

[radhermit]

I need to do a lot of work updating the C bindings for all the redesigned pkgcraft functionality in the last ~6 months (namely the build process pool) and then into all the other language bindings probably changing a decent amount of the config and/or repo facing API as I do.

As it's really not an enjoyable process overall I haven't done it yet. 😆

[radhermit]

if a newer version than sys-apps/pkgcraft-tools-0.0.17 is installed.

Also, I'm not sure how this could be true as all the pkgcraft-related tools are rust-based and thus all build their own versions of pkgcraft so pkgcraft-tools has no bearing on the pkgcraft-python bindings... sys-libs/pkgcraft does but generally that shouldn't be specifically installed unless one is looking to directly use the C API.

[Flowdalic]

Sorry, I blamed sys-apps/pkgcraft-tools, while it is actually sys-libs/pkgcraft

sys-libs/pkgcraft does but generally that shouldn't be specifically installed unless one is looking to directly use the C API.

That is why am I doing (actually accessing pkgcraft's C API via JNA for Java/Scala). :)

I am using sys-libs/pkgcraft-9999 atm, downgrading fixes that. I just assumed that the combination of all pkgcraft -9999 ebuilds is possible. Especially since dev-pyhton/pkgcraft-9999 declares a dependency >=sys-libs/pkgcraft-9999. But this is probably now a bug in the ebuild.

[radhermit]

Sorry, I blamed sys-apps/pkgcraft-tools, while it is actually sys-libs/pkgcraft

No problem, I figured you just mistyped but wanted to correct it anyway. 😄

sys-libs/pkgcraft does but generally that shouldn't be specifically installed unless one is looking to directly use the C API.

That is why am I doing (actually accessing pkgcraft's C API via JNA for Java/Scala). :)

Oh, that sounds cool. Maybe it'll help inspire me to update the C bindings then as I assumed few to no people were using them so far, with only people mostly poking at pk repo metadata and maybe looking at pkgcruft occasionally.

I am using sys-libs/pkgcraft-9999 atm, downgrading fixes that. I just assumed that the combination of all pkgcraft -9999 ebuilds is possible. Especially since dev-pyhton/pkgcraft-9999 declares a dependency >=sys-libs/pkgcraft-9999. But this is probably now a bug in the ebuild.

It generally is and should be, but I've been slacking on getting the bindings working for the most recent pkgcraft changes... it's a lot of work. That being said, I'll try to find the time and inspiration to pull them up to date within the next month.