@vishwin please fix this up and after that also D34739, before working on any new stuff.

Doing it this way, when building meson-python on a non-default Python, fails because literally bin/meson is expected, not bin/meson-${PYTHON_VER}.

Don't even think about un-flavouring everything, near future consumers need to use this with all supported Python.

In D39004#888511, @vishwin wrote:

Doing it this way, when building meson-python on a non-default Python, fails because literally bin/meson is expected, not bin/meson-${PYTHON_VER}.

Don't even think about un-flavouring everything, near future consumers need to use this with all supported Python.

So the default-python based package can additionally install everything under plain names, or there can be another package that depends on the default python's and adds symlinks to the relevant entry points, commands, documentation, without all those 39 and -3.9 names.

In D39004#888526, @mandree wrote:

So the default-python based package can additionally install everything under plain names, or there can be another package that depends on the default python's and adds symlinks to the relevant entry points, commands, documentation, without all those 39 and -3.9 names.

Not tenable since meson-python has to operate under the same Python version/distribution, which is checked and enforced during the build process.

In D39004#888503, @vishwin wrote:

add USE_PYTHON=concurrent and remove polkit action, as it file conflicts and doesn't work properly here anyway

Looks incomplete. patch-setup.py was adjusting manpage location, obsoleted by 003a571d1d65. To fix polkit action may require either expanding USES=uniquefiles:dirs (implied by USE_PYTHON=concurrent) to handle the conflicting file/directory or adjusting ${TMPPLIST} from post-patch gated by PKGNAMESUFFIX.

$ pkg install meson
$ pkg install meson-py311
[...]
Checking integrity... done (1 conflicting)
  - meson-py311-1.0.1_1 conflicts with meson-1.0.1_1 on /usr/local/share/polkit-1/actions/com.mesonbuild.install.policy
Checking integrity... done (0 conflicting)
The following 4 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        meson: 1.0.1_1
[...]

In D39004#888542, @jbeich wrote:

Looks incomplete. patch-setup.py was adjusting manpage location, obsoleted by 003a571d1d65. To fix polkit action may require either expanding USES=uniquefiles:dirs (implied by USE_PYTHON=concurrent) to handle the conflicting file/directory or adjusting ${TMPPLIST} from post-patch gated by PKGNAMESUFFIX.

The action itself is effectively a sudo make install wrapper for those who did not already temporarily elevate their privileges. The referenced paths, which are hardcoded as /usr, are wrong for us. Port builds don't use this at all.