v26.06rc1: configure: uv: not found

[whitslack]

2599c09 seems misguided, as it fails to work correctly on systems lacking uv:

./configure: 119: uv: not found
./configure: 119: uv: not found
./configure: 119: uv: not found
./configure: 119: uv: not found
./configure: 119: uv: not found

Then, during the build, running msggen fails because the Python interpreter was not correctly detected:

PYTHONPATH=contrib/msggen  contrib/msggen/msggen/__main__.py bundle doc/schemas
/bin/sh: 1: contrib/msggen/msggen/__main__.py: Permission denied
make: *** [contrib/msggen/Makefile:15: contrib/msggen/msggen/schema.json] Error 126

(Notice the extra space between PYTHONPATH=contrib/msggen and contrib/msggen/msggen/__main__.py. That's where the Python interpreter command name is supposed to go.)

uv is not a hard dependency for building CLN, even if one wants the Python components. Gentoo is now resorting to stripping out the extraneous uv run tokens from configure, but an upstream solution would be preferable.

[rustyrussell]

Huh: I had assumed uv was a required dependency. How are you ensuring you have the required Python packages? I know other tools can read pyproject.toml, or you could be doing it manually?

[whitslack]

How are you ensuring you have the required Python packages?

Portage (Gentoo's default system package manager) or any other PMS-compliant package manager. You can see all the Python dependencies listed in the Core Lightning ebuild here. The package manager ensures that these packages are installed on the system (if needed according to the user's chosen configuration options) before it will attempt to build Core Lightning.

Uv and other attempts to reinvent the wheel like Pip are frowned upon in Gentoo because they do not integrate with the system package manager.