libpsl, python and dependecies

[Vincent Habchi]

Folks,

Libpsl has been recently updated (June 25, commit a7d5d5e3a1d4a17f9141018dc948e474f2f867d9) but still drags a dependency on Python 3.10, which is awful.

In the Portfile, we find this comment:

# Please note this port is (indirectly, via cmake) a dependency of the
# various clang-X ports. When updating the port versions (e.g. python)
# used here make sure to ensure that the new port being used uses the
# clang_dependency PortGroup to avoid circular dependencies whilst building.
# See e.g. https://trac.macports.org/ticket/60419

In fact, Python 3.10 portfile is member of the clang-dependency group:
—
PortSystem 1.0
PortGroup clang_dependency 1.0

name                python310
—

But as far as I can see, this has never been propagated to more recent python portfiles:

3.11:
—
PortSystem 1.0

name                python311
—
[…]
3.14:
—
PortSystem 1.0

name                python314
—

Is the cycle handled in another way, or should we add clang_dependency membership for all python Portfiles >= 3.11 and change the libpsl Portfile to avoid explicit Python 3.10 dependency which is totally unjustified technically-wise?

Vincent