On Tue, 26 Jul 2016, Mike Hommey wrote: > One thing that is sadly missing in all this is the notion of whether the > installed package can be meaningfully be used. That is :any would also > allow to install firefox-esr:mips, but it won't do you any good...
In general a foreign architecture is only enabled when it's usable and I don't have any reason to micro-manage which architecture should be usable... if the user wants firefox-esr:i386 on amd64, then so be it. So I prefer the ":any" approach. > Can't you add a dependency like "firefox-esr:armhf [arm64] | firefox-esr"? That's (roughly) the work-around that I'm using currently. Except that that armhf is not available at image build time so the native firefox-esr is always installed. I just wanted the user to be able to install the armhf one in place of the default arm64 one without impacting the meta-packages he has installed. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
