empty build commands for meson

[christianrauch]

I am trying to generate the module build commands for meson via ./flatpak-pip-generator meson but the resulting commands in python3-meson.json are empty:

{
    "name": "python3-meson",
    "buildsystem": "simple",
    "build-commands": [],
    "modules": []
}

The log does not show warnings or errors:

========================================================================
Downloading sources
========================================================================
Running: "pip3 download --exists-action=i --dest /tmp/pip-generator-python3-mesons8em0uta -r /tmp/requirements.1mcyjcl7"
Collecting meson
  Using cached meson-0.61.0-py3-none-any.whl (849 kB)
Saved /tmp/pip-generator-python3-mesons8em0uta/meson-0.61.0-py3-none-any.whl
Successfully downloaded meson
========================================================================
Downloading arch independent packages
========================================================================
========================================================================
Obtaining hashes and urls
========================================================================
Generating hash for meson-0.61.0-py3-none-any.whl
Extracting download url for meson
========================================================================
Generating dependencies
========================================================================

Output saved to python3-meson.json

[gasinvein]

This is probably because Meson is already present in the SDK. Why do you need to generate it?

[christianrauch]

I wanted to install a newer version of meson.

[TingPing]

For now you can manually edit it out here: https://github.com/flatpak/flatpak-builder-tools/blob/master/pip/flatpak-pip-generator#L297

We should add a flag to override system versions though.

[christianrauch]

That explains why this is ignored entirely. Why are those packages blacklisted? Isn't it reasonable to assume that, if a user chooses to install a pip package manually, it is because a newer version is required? Also, there are other runtimes where this does not apply. So I think it is better to remove that blacklist entirely and let the user decide which packages to add to the flatpak.

[TingPing]

Isn't it reasonable to assume that, if a user chooses to install a pip package manually, it is because a newer version is required?

Yes I think that is fine and should be changed.

The list prevents other packages pulling in setuptools for example which is already installed.

Also, there are other runtimes where this does not apply.

Nothing that is a supported version.

[christianrauch]

Even after removing meson from the blacklist, it is not installed correctly and the system/sdk version still takes precedence:

ERROR: Meson version is 0.59.4 but project requires >=0.60.0