Architecture-specific sources for parts

[Evan]

Applications snap up great when the ISV/upstream already provides pre-compiled binaries. That is, until you want to support multiple architectures.

Sergio designed this here, but the card was re-scoped to just cover architecture-specific stage packages:
https://trello.com/c/yBFYmonw/49-support-per-architecture-entries-in-stage-packages#comment-581b4b593f68e9c0ba861fa3

This would benefit many upstreams, particularly traefik.

[elespike (elespike)]

Affects me because I'm helping the Rocket.Chat team on multi-arch support and we need to point to different sources depending on architecture, especially in order to maintain backward compatibility.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I'm also affected by this when pulling in debs which are architecture specific dependencies of a main part.

[Michael Schnaitter (kj4tbt)]

I am affected by this when pulling in archives containing binaries that are architecture specific

[Omer Akram (om26er)]

Sublime text upstream provides precompiled binaries for different arches, so this feature will be really helpful there.