[Feature Request]: Different source for different architectures
Metadata
Current evaluation
Resolved via maintainer workaround using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The author accepted the solution, and the issue was closed.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Provide a mechanism for using different source on different architectures.
```yaml
parts:
my-app:
plugin: dump
source-type: deb
source:
# If I run `snapcraft build` on amd64, it will use amd64 version of deb as source.
amd64: target/my-app_1.0.0_amd64.deb
# Or if I run on arm64, another deb will be used.
arm64: target/my-app_1.0.0_arm64.deb
riscv: target/my-app_1.0.0_riscv.deb
```
### Why it needs to get done
Hi community, 👋🏼 I'm a collaborator (only **Triage**, without write access) of repository [clash-verge-rev/clash-verge-rev](https://github.com/clash-verge-rev/clash-verge-rev).
I'd like to implement an integration of GitHub Workflows to build a `.snap` for the application. In previous jobs & steps, we already built and signed `*.deb` files for users. Those steps are running using strategy matrix on `ubuntu-22.04` with different architectures (`amd64` and `arm64`). Built release also have these kinds of suffix (`_amd64.deb` and `_arm64.deb`).
We want to build different snaps for different architecture, so different architecture uses different `source` in `snapcraft.yaml` parts. Is this currently supported? Or can community implement this feature? 🙏🏼
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Resolved via maintainer workaround using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The author accepted the solution, and the issue was closed. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved. Maintainer provided a working workaround using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The feature request is closed as unnecessary. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by recommending the CRAFT_ARCH_BUILD_FOR environment variable in the source path to dynamically select architecture-specific files. The contributor verified the workaround works, and the issue was closed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via a workaround using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The author confirmed compatibility and will implement it. Closed without code changes. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved by using the $CRAFT_ARCH_BUILD_FOR variable in the source path to dynamically select architecture-specific deb files. The author confirmed this works with their workflow, and the issue was marked resolved. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #93 Automatically use source package's architectures in non-native mode | debcraft | open | Feature request for debcraft non-native mode to read debian/control to determine target architectures instead of defaulting to all standard platforms. Open, unlabelled, no maintainer comments, inactive for 179 days. |