meson plugin uses internet access during build, instead of pull
Metadata
Current evaluation
Meson plugin runs pip install during build stage instead of pull, consuming network time on RISC-V builds. 4.5 years old, zero comments, no labels, no maintainer response. Author planned to work around it manually.
Suggested action: needs triage
Reason: Issue has no labels, zero comments, and no maintainer interaction in 4.5 years, so it has never been triaged. The underlying concern (pip install during build vs pull in the meson plugin) is a valid architectural question, but I could not verify via code inspection whether the current meson plugin still exhibits this behavior, so a maintainer needs to confirm relevance before closing or fixing.
Impact:
40
Quick Win:
22.0
Staleness:
92
Complexity:
45
Confidence:
55
Support Request:
15
Issue body
meson plugin uses internet access during build, instead of pull
It generates build command:
/usr/bin/python3 -m pip install -U {meson_package}
Ideally that should be pulled-in during pull stage
I think I will have to unroll meson plugin, and do what it does by hand, such that I can shuffle `pip install` during override-pull, instead of during build.
As I am running out of network access time during riscv builds with meson.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22.0
Staleness:
92
Complexity:
45
Confidence:
55
Support Request:
15
|
needs triage | Meson plugin runs pip install during build stage instead of pull, consuming network time on RISC-V builds. 4.5 years old, zero comments, no labels, no maintainer response. Author planned to work around it manually. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Meson plugin executes pip install during build instead of pull, causing network limits for RISC-V builds. Unlabelled, inactive for over 4 years, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
30
|
close stale | Meson plugin runs pip install during build instead of pull, causing network constraints. Unaddressed for over four years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
40
|
close stale | Feature request to move meson package installation from build to pull stage to save network time. Issue is 4+ years old with no maintainer response or follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
15
|
close stale | Feature request to move meson plugin pip installation from build to pull phase to reduce network usage during riscv builds. Issue has no maintainer interaction, labels, or comments after over 4 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1957766 plugin:meson is not installed during pull stage | snapcraft (launchpad) | open | snapcraft 6.0.1: plugin:meson parts are not cached during the pull stage, so the build stage must fetch meson over the network and the proxy times out. Reported by xnox, open ~4.6 years with no labels, comments, or maintainer response. |