if the base is already installed, do not add as build-snap
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Resolved via snapcraft PR #2384. The change prevents adding the base snap as a build-snap when it is already installed on the host, enabling direct host snap injection.
Suggested action: —
No scores available.
Issue body
This allows use of injecting the snap that corresponds to what is installed on the host.
https://github.com/snapcore/snapcraft/pull/2384
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Resolved via snapcraft PR #2384. The change prevents adding the base snap as a build-snap when it is already installed on the host, enabling direct host snap injection. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by merging pull request #2384. The update prevents adding an already installed base as a build-snap, enabling injection of the host-installed snap instead. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via merged pull request #2384. The update prevents adding an already installed base snap as a build-snap, enabling injection of the host-installed snap instead. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4983 Install base snap if declared as `build-base` | snapcraft | closed | Closed as superseded. Base and build-base combination restrictions in #4878 render this enhancement moot. The author acknowledged the change and implemented a workaround. Implementation may be revisited for kernel snap interim base support. |