Install base snap if declared as `build-base`
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
### What needs to get done
A base snap, when declared as the `build-base` for a snap, should be installed in the build environment as it is with regular bases declared as `base: coreXX`.
I would only expect this installation to occur just in case the build-base snap actually exists. For instance, `devel` is a special case, where that base only *sometimes* exists (currently `devel` is 24.10, but that base doesn't exist (and won't).
Likewise, this should not apply to interim releases in general (as those will one day be supported for kernel snaps).
### Why it needs to get done
As the `build-base` defines a build-time environment, it arguably makes *more* sense that the `build-base` is installed than the `base`. Indeed, kernel snaps are only ever built with a `build-base`, and installing the build-base into the environment will improve support for e.g. the new initrd plugin (which copies `/etc/os-release` from the build-base).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by base/build-base combination restrictions (#4878). The enhancement is unnecessary; the author acknowledged the change and implemented a workaround. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as abandoned. The enhancement was deemed moot due to upcoming base/build-base combination restrictions (#4878). The author agreed and implemented a workaround instead. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded pending #4878 base and build-base combination restrictions. Maintainers will revisit base installation logic when implementing interim base support for kernel snaps. Author acknowledged and implemented a workaround. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Deferred and closed. The build-base installation enhancement was postponed pending issue #4879 restrictions. The author found a workaround, and maintainers will revisit base installation when supporting interim kernel snap bases. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4868 Allow specifying build-base in kernel snap | snapcraft | closed | Implemented as a prototype in a feature branch via pull request #4914, enabling kernel snaps to specify build-bases using the standard cross-craft naming system. | |
| #1819196 support for build-base | snapcraft (launchpad) | closed | Closed without implementation. The request to add build-base support for static snaps and kernels in Launchpad was abandoned after years of inactivity. | |
| #5095 Support interim build bases for kernel snaps | snapcraft | closed | Closed as a duplicate of issue #4878. The request to support interim kernel bases was superseded by the referenced tracking issue, which consolidates the feature requirements and platform dependencies. | |
| #2689 schema: build-base support for the snapd type | snapcraft | merged | Merged into master. Implements build-base keyword support for the snapd snap type, enabling its construction. Approved by reviewer, passed CI, and updated four files. | |
| #6177 feat: allow building stable base snaps | snapcraft | closed | Closed and superseded in favor of pull request #6147 and a separate branch for early core26 enablement. The feature to build stable base snaps was not merged directly but redirected to the referenced PR. | |
| #1799842 if the base is already installed, do not add as build-snap | snapcraft (launchpad) | closed | 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. | |
| #1835532 snapcraft behavior for type: base | snapcraft (launchpad) | closed | Closed without comments. The type: base and build-base configuration behavior was superseded by updated snapcraft core20 implementation. | |
| #1659 Implement support for supported bases | snapcraft | closed | Closed without implementation or discussion. The multi-base support request was abandoned and likely superseded by later snapcraft updates that expanded base compatibility. | |
| #4914 feat: allow interim bases for kernel snaps | snapcraft | merged | Merged after approval and CI checks. Adds interim base support for kernel snaps, updates documentation and tests, and resolves #4868. Changes how kernel snaps define bases and build-bases. |