Put environment in command-chain instead of the opaque wrapper
Metadata
Current evaluation
Fixed by merged PR snapcore/snapcraft#2291 (commit e0f567833), moving plugin environments and runnables from opaque per-app wrappers into a dedicated runner.
Resolution: closed resolved
Reason: PR #2291 was merged as commit e0f567833, placing environment setup in the runner rather than each app wrapper in preparation for command-chain support.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The snapcraft CLI currently takes all the plugin environments and runnables and shoves them into wrappers for every app. Prepare for the move to command-chain by putting this information in a separate binary instead.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR snapcore/snapcraft#2291 (commit e0f567833), moving plugin environments and runnables from opaque per-app wrappers into a dedicated runner. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2291 (commit e0f567833, 'meta: put environment into runner instead of app wrapper'), which moves plugin environment/runnables from per-app wrappers into a dedicated runner script ahead of command-chain work. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved in merged PR #2291 (e0f567833): moved plugin environment and runnables from per-app wrappers into a dedicated runner ahead of command-chain. | |
| qwen/qwen3.6-35b-a3b | — | — | Implemented the migration of plugin environments and runnables from opaque wrappers to a separate binary for command-chain support. The task was completed and the issue closed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and implemented as part of the command-chain migration. Environment configuration was moved to a separate binary, replacing the opaque wrapper approach for snapcraft applications. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments. The change was abandoned or superseded, with the command-chain migration presumably completed elsewhere. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and implemented. Plugin environments and runnables were moved from opaque wrappers to a separate binary to support the command-chain architecture migration. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcore/snapcraft#2291
(confidence 100%)
The issue comment links this PR, whose merged commit e0f567833 implements the proposed runner-based environment setup.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2291 meta: put environment into runner instead of app wrapper | snapcraft | merged | Merged #2291, moving plugin environment and runnables from per-app wrappers into a dedicated runner; resolved LP #1794261 in commit e0f567833. | |
| #3741 parts: replace snapcraft command-chain with environment | snapcraft | merged | Merged #3741 as ec190695c, replacing core22 snapcraft_runner command-chain handling with command-chain and global LD_LIBRARY_PATH/PATH defaults while deprecating adapter. | |
| #1824255 snapcraft should use command-chain for hooks | snapcraft (launchpad) | closed | Fixed hook environment setup in merged #2897 (bfac28cea) by embedding the generated snap environment in hook wrappers; released in Snapcraft 3.10. |