snapcraft 7.x/edge generates command-chain executables even when all apps and hooks use adapter:none
Metadata
Current evaluation
snapcraft 7.x/edge primed a command-chain wrapper even with all apps/hooks using adapter:none. Fixed by PR #3741 (commit ec190695c), released in snapcraft 7.0.1.
Resolution: closed resolved
Reason: Maintainer ~mr-cal linked the fix to snapcore/snapcraft PR #3741, which was merged as commit ec190695c replacing the snapcraft command-chain wrapper with hook-based handling and global LD_LIBRARY_PATH/PATH defaults, and confirmed it was released in snapcraft 7.0.1.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I was trying to slim a snap that uses just a statically linked binary, so that I could move to the bare snap as a dependency.
Even when all the apps use adapter:none, snapcraft generates the command chain wrapper. For the record, the meta/snap.yaml file did *not* reference the wrapper (on edge, candidate was broken as 2022-05-12) so this was just uneeded file I had no way to remove.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | snapcraft 7.x/edge primed a command-chain wrapper even with all apps/hooks using adapter:none. Fixed by PR #3741 (commit ec190695c), released in snapcraft 7.0.1. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft stopped generating an unused command-chain wrapper for adapter:none projects via canonical/snapcraft#3741 (ec190695c), released in 7.0.1. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in snapcraft#2912 (commit f9475e6f1) by skipping command priming for adapter:none apps, removing the unused snapcraft-runner executable. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The issue reported snapcraft 7.x/edge generates unnecessary command-chain wrappers despite adapter:none configuration. Zero comments and no linked fixes confirm no action was taken. | |
| qwen/qwen3.6-35b-a3b | — | — | Snapcraft generating unnecessary command-chain wrappers despite adapter:none configuration was abandoned and closed without resolution. No comments or fixes were provided. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#3741
(confidence 95%)
PR cited in the closing maintainer comment; merged as commit ec190695c, shipped in 7.0.1
-
Related To:
canonical/snapcraft#3296
(confidence 45%)
Earlier commit 95225991f added command-chain stubs via hooks, the mechanism #3741 builds on
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #2836 meta: fix command-chain handling when Application adapter == "none" | snapcraft | closed | PR #2836 was closed unmerged on 2020-01-07 by author cjp256 in favor of a simpler back-portable PR #2853, which was merged (commit 9599497fb) and fixed adapter: none adding snapcraft-runner to command-chain. | |
| #1798918 command-chain is incompatible with legacy adapter, but snapcraft doesn't say so | snapcraft (launchpad) | closed | Added a sanity check rejecting command-chain use with the legacy app adapter in snapcore/snapcraft#2375 (commit 57c7fb8d0). |