https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296086
--- Comment #10 from Charlie Li <[email protected]> --- Yes, as I said in comment 1, the expected binary is exactly `meson`, nothing else. (In reply to Tatsuki Makino from comment #6) https://mesonbuild.com/meson-python/reference/pyproject-settings.html#cmdoption-arg-tool.meson-python.meson So theoretically Blender's pyproject.toml could be patched to add this setting to specify the correct meson executable. The environment variable overrides that setting. Otherwise this is normally used to specify a forked/vendored meson in the same source tree of a package, like with numpy. Because of existing legitimate use cases like numpy, the environment variable should never be specified for ports. However, I'm still not convinced for USE_PYTHON=concurrent here because the polkit file still exists. Have to consider that meson itself can be used outside of the ports context, on hierarchies that pkg(8) does not manage but still owned by a different user/group. polkit is another privilege escalation option that may be more suitable than sudo or other supported methods. -- You are receiving this mail because: You are the assignee for the bug.
