* Johannes Schauer <jo...@debian.org>, 2015-05-25, 13:39:
http://lists.debian.org/20141217084500.ga16...@alf.mars
In your case this would mean that the source package building
libfoo-dev would modify the binary package libfoo-dev to Provides:
optional-libfoo-dev and additionally build a binary package called
no-libfoo-dev on all architectures where libfoo-dev is *not* built
which also Provides: optional-libfoo-dev. Lastly, let your source
package build depend on optional-libfoo-dev.
This solution might have a slight advantage over the one one proposed
by Jakub
It has a big advantage: unlike mine, it actually works. :-P
But Helmut's approach only works if libfoo maintainer knows in advance
the list of architectures where libfoo-dev will be built. It can't be
applied if, say, libfoo build-depends on libbar-dev, and libbar-dev
hasn't been built everywhere.
--
Jakub Wilk
--
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/20150525140039.ga7...@jwilk.net
