+++ Sebastian Reichel [2014-12-11 21:25 +0100]:
> Hi,
> 
> 
> How about building for "arch: any" and adding a build dependency
> on a new "efi-support" package, that is only available for
> architectures with efi available?

That is a sensible suggestion. It keeps the ecosystem of 'efi stuff'
more self-contained than involving dpkg. If it was expected to change
frequently this would probably work better in practice.

However it does leave the depending packages listed as
'BD-uninstallable' on the non-efi architectures, which gives the
impression that one day they _should_ appear, which is not really the
case here.

efi-any (as an architecture group) would correctly list things as
'not-for-us' on the unsupported architecture.

Not a huge practical difference, but suggests to me that efi-any as an
architecture-group is a better fit.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141212120723.gg27...@stoneboat.aleph1.co.uk

Reply via email to