remote-build: Support passing --enable-experimental-extensions & options in general
Metadata
Current evaluation
Valid request for remote-build to forward Snapcraft options, blocked on Launchpad API support; the original core20-specific use case is now obsolete.
Suggested action: needs triage
Reason: The request has maintainer acknowledgement, but maintainers said it requires Launchpad API support and explicitly identified launchpad#1949989 as the separate upstream task, so the open state here is misleading. Scope also needs reassessment: core20 is no longer current, and experimental extensions are now enabled with the SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS environment variable rather than the removed command-line flag.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
4
Complexity:
78
Confidence:
91
Actionability:
55
|
needs triage | Valid request for remote-build to forward Snapcraft options, blocked on Launchpad API support; the original core20-specific use case is now obsolete. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
5
Complexity:
72
Confidence:
91
Actionability:
46
|
keep open | remote-build cannot pass Snapcraft options to Launchpad, blocking experimental-extension builds until Launchpad API support is available | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
6
Complexity:
55
Confidence:
78
Actionability:
38
|
needs triage | Request for remote-build to forward Snapcraft options, including --enable-experimental-extensions for KDE Neon on core20; support depends on Launchpad LP#1949989. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
16
Staleness:
90
Complexity:
55
Confidence:
65
Support Request:
30
|
close stale | Feature request to pass snapcraft options (e.g. --enable-experimental-extensions) to remote-build, blocked on Launchpad bug 1949989. The motivating kde-neon core20 case is resolved as the extension is no longer experimental. No activity for ~4.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to allow passing arbitrary snapcraft options like --enable-experimental-extensions to remote-build. Unaddressed for over 4 years with zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Feature request to allow passing custom snapcraft options like --enable-experimental-extensions to remote-build. Unaddressed and inactive for over 4 years with zero maintainer interaction. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
80
Support Request:
5
|
needs triage | Feature request to allow passing arbitrary options like --enable-experimental-extensions to snapcraft during remote-build. Unlabelled, zero maintainer comments, inactive for over four years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Blocked By:
launchpad#1949989
(confidence 100%)
The body links this Launchpad issue, and a maintainer confirmed that its API work is tracked separately.
-
Superseded By:
snapcraft#3266
(confidence 95%)
The merged expand-extensions option added the old CLI flag, but current Snapcraft instead documents the environment-variable activation path.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2933 remote-build: introduce --launchpad-snapcraft-channel option | snapcraft | closed | Closed unmerged; PR #2938 superseded the CLI-toggle approach by making remote builds default to Snapcraft's stable channel, merged as 534ee1c1f. | |
| #4093 cli: add option to enable experimental plugins for snapcraft_legacy | snapcraft | merged | Merged in snapcore/snapcraft#4093 (937e52959), adding core18/core20 support for experimental extensions via the CLI option or environment variable in snapcraft_legacy. |