build provider support to inject snaps on the host
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned. The request to inject snaps into build providers when running snapcraft from a snap was closed without implementation due to prolonged inactivity and no further development.
Suggested action: —
No scores available.
Issue body
When running snapcraft from a snap, the build provider should inject the snap into the running provider.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The request to inject snaps into build providers when running snapcraft from a snap was closed without implementation due to prolonged inactivity and no further development. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The request to inject snaps into build providers received no comments or implementation and was likely abandoned or superseded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Lacking discussion or activity, the request was abandoned and superseded by evolved build provider architectures that handle snap injection differently. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1779138 build provider runner detection | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned. Outlines a requirement to install the snapcraft snap instead of injecting it when the build provider runs outside a snap. No fix or follow-up was recorded. | |
| #2174 build_providers: inject snaps when running from a snap | snapcraft | merged | Merged. Updates build providers to inject snapcraft and its base from the host when running inside the snapcraft snap, ensuring parity with non-snap environments. Approved by reviewer and passed CI checks. | |
| #1779136 build provider support to clean parts | snapcraft (launchpad) | closed | Build provider support for cleaning parts when using the base entry in snapcraft.yaml was closed and abandoned without implementation. | |
| #1779135 build provider support for lifecycle steps | snapcraft (launchpad) | closed | Closed without implementation. The request to pass lifecycle commands to build providers when using the base entry in snapcraft.yaml was abandoned. No comments or resolution details were provided. | |
| #4706 Install build snaps from the host if available | snapcraft | open | Feature request to inject host-installed build snaps into the build container to speed up development and avoid re-downloading large SDK snaps. Active: a maintainer recently proposed using craft-application's enqueue_snap_injection. | |
| #1805219 Support for looking in build-aux/snap | snapcraft (launchpad) | closed | Closed without implementation. The request to prioritize build-aux/snap over snap for snapcraft definitions was abandoned. | |
| #1677974 snap build dependencies | snapcraft (launchpad) | closed | Closed without resolution. The request to specify snap packages as build dependencies in snapcraft.yaml appears abandoned or superseded by upstream Snapcraft updates that later added native build dependency support. | |
| #1789206 cannot rebuild snapcraft | snapcraft (launchpad) | closed | Closed without resolution. The request to enable snapcraft self-rebuilding via build caching was abandoned due to prolonged inactivity and lack of implementation. | |
| #1599578 Snapcraft cloudbuild | snapcraft (launchpad) | closed | Feature request for external server-based snap builds via Juju or CI tools was closed and abandoned. No implementation or discussion occurred. |