snapcraft needs to migrate to a snap directory
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 proposed migration of snapcraft to a snap directory, including build artifact relocation and plugin updates, was abandoned or superseded by subsequent architecture changes.
Suggested action: —
No scores available.
Issue body
Tasks involve:
- add the option for snapcraft to live in snap/snapcraft.yaml
- parts, stage and prime moving parts need to be in snap
- building blocks need to be available in the resulting snap in a snap directory (hidden with a feature flag).
- plugins need to migrate to this snap directory.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The proposed snap directory migration was abandoned and superseded by subsequent snapcraft architecture updates. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The proposed snapcraft directory migration, including relocating build artifacts and updating plugins, was abandoned. Later snapcraft versions adopted equivalent structural changes. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1069 snapcraft.yaml and building in snap directory | snapcraft | closed | Closed without merging. The maintainer reviewed the snapcraft.yaml and build directory changes but opted to close the pull request to de-clutter the repository. | |
| #1498140 snapcraft run should only run from the project directory | snapcraft (launchpad) | closed | Closed without implementation. The request to restrict snapcraft run to the project directory was abandoned or superseded by later design changes, with no discussion or resolution details provided. | |
| #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. | |
| #1674952 snapcraft tour broken when installed from snap | snapcraft (launchpad) | closed | The snapcraft tour command failed due to a missing directory path when installed via snap. The issue was closed without comments or documented resolution, indicating it was abandoned or fixed in a later release. | |
| #1794497 Snapcraft can't re-use build VM if anything went wrong with the initial setup | snapcraft (launchpad) | closed | Closed and likely abandoned. Snapcraft lacks automatic recovery for failed VM setups, forcing manual cleanup. No resolution was provided, suggesting the issue was superseded by updated build environment handling. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1699 snapcraft <help> command | snapcraft | closed | Closed without implementation or discussion. No resolution or merge details were provided, indicating the snapcraft help command feature request was abandoned. | |
| #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. | |
| #1615764 Support snapcraft close | snapcraft (launchpad) | closed | The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening. | |
| #1793261 Vendor legacy snapcraft to maintain backward compatibility | snapcraft (launchpad) | closed | Closed without implementation. The proposal to vendor legacy snapcraft for backward compatibility was abandoned. No comments or resolution details were provided, indicating the approach was likely superseded by later snapcraft architecture changes. |