snap build dependencies
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
No scores available.
Issue body
Compilers and interpreters are starting to arrive as snap packages. Unfortunately, we can't use them for many projects because there is no way to specify them as build dependencies in snap.yaml and we are stuck using the deb packages.
We need to list build dependencies that are snaps in snapcraft.yaml, so that snapcraft can install them if necessary, so that they can be used to build snaps with Launchpad or 'snapcraft cleanbuild'
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | A feature request for specifying snap packages as build dependencies in snapcraft.yaml was closed without comments or implementation. The request appears abandoned or superseded by later tooling updates. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. The request to declare snap packages as build dependencies in snapcraft.yaml was closed without implementation or discussion. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1688151 snapcraft pull doesn't save the installed build dependencies | snapcraft (launchpad) | closed | Closed without comments or resolution. The bug where snapcraft pull omitted build package dependencies from the pull state file was abandoned. | |
| #1448 snapcraft build using manifest.yaml | snapcraft | closed | Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded. | |
| #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. | |
| #1544137 consider adding build-essential to the depends of snapcraft package (fails to build simple C program in fresh classic) | snapcraft (launchpad) | closed | Closed without action. The proposal to add build-essential as a snapcraft package dependency was abandoned due to lack of discussion. No implementation occurred. | |
| #1675516 can't cleanbuild snapcraft itself | snapcraft (launchpad) | closed | Closed without resolution or comments, the report of a failed snapcraft cleanbuild due to missing build-packages was abandoned. | |
| #2020683 snapcraft remote-build cannot use a custom version of snapcraft | snapcraft (launchpad) | closed | Request to enable custom snapcraft versions in remote-build was closed without implementation. No resolution or merge details were provided, indicating the feature was abandoned. | |
| #1610910 cleanbuild needs to support apt proxy config | snapcraft (launchpad) | closed | Closed without resolution or discussion. The apt proxy configuration request for snapcraft cleanbuild was abandoned due to lack of engagement and evolving build tooling. | |
| #1778081 Snapcraft saves the fact that parts need to be rebuilt rather than discovering them | snapcraft (launchpad) | closed | Closed without implementation. The dynamic dependency discovery approach for build caching was abandoned and superseded by later Snapcraft caching architecture updates. | |
| #1659085 snapcraft needs to migrate to a snap directory | snapcraft (launchpad) | closed | Closed without resolution. The proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes. | |
| #2086482 No way to express different build dependencies on different architectures without repetition of the list of dependencies | snapcraft (launchpad) | open | Feature request: snapcraft YAML grammar lacks support for architecture-specific build dependencies without repetition. No maintainer response after 671 days. |