Investigate proper support for "build-for: all"
Metadata
Current evaluation
Core24 will not support build-for: all; maintainers found true architecture independence uncommon and consider per-architecture snaps or remote builds sufficient.
Resolution: closed not a bug
Reason: In his closing comment dated 2024-04-25, maintainer mr-cal explicitly decided not to support build-for: all in core24. The stated alternatives are separate per-architecture snaps and remote builds on supported architectures.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
We're (temporarily) disabling support for `build-for: all` in core24 because we need to revisit/investigate what a "correct" multiplatform snap looks like.
### Why it needs to get done
The feature as it is right now in core22 is not really "multi-platform"
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Core24 will not support build-for: all; maintainers found true architecture independence uncommon and consider per-architecture snaps or remote builds sufficient. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed without code changes: maintainers rejected build-for: all for core24, favoring per-architecture snaps and remote builds because truly architecture-independent snaps are rare. | |
| stealth/space-bunny-alpha | — | closed not a bug | Core24 support for `build-for: all` was rejected because few snaps are truly architecture-independent; remote-build and per-architecture snaps cover the need. | |
| qwen/qwen3.6-35b-a3b | — | — | Support for build-for: all was rejected in core24 due to limited demand for architecture-independent snaps. Alternatives like per-arch builds and remote-build suffice. The feature remains disabled; users should file new tickets for specific use cases. | |
| qwen/qwen3.6-35b-a3b | — | — | Support for build-for all was rejected for core24 due to limited multi-platform use cases and architecture-dependent dependencies. The feature was disabled, directing developers to use architecture-specific builds. | |
| qwen/qwen3.6-35b-a3b | — | — | build-for: all support was rejected for core24. Decision cites limited architecture-independent use cases, sufficient separate arch snaps, and existing remote-build capabilities. New tickets required for specific user stories. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Support for build-for: all in core24 was disabled and rejected. Limited architecture-independent use cases and viable alternatives like separate architecture snaps and remote build led to this decision. New tickets required for specific needs. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4854 Accept `build-for: [all]` and `--build-for=all` for architecture-independent snaps | snapcraft | closed | Resolved: Snapcraft supports build-for [all] and --build-for=all for remote builds/core24 in 8.4.0 and core22 in 8.7.0; requested core22/core24 regression tests were added. | |
| #4873 feat: support "build-for: [all]" in core24 | snapcraft | merged | Merged PR #4873 as commit 319056d7a, adding core24 support for build-for: [all] and fixing #4854. The feature shipped in Snapcraft 8.4.0. | |
| #3821 meta: architectures | snapcraft | merged | Merged core22 architecture support, including build-on/build-for handling, host and build-instance selection, and SNAPCRAFT_BUILD_FOR filtering, via commit 4876b53. |