On Mon, Jun 22, 2009 at 5:43 PM, Russ Allbery<r...@debian.org> wrote: > Mathieu Malaterre <mathieu.malate...@gmail.com> writes: > >> Let's consider one source package 'foo' which can be build using a >> --enable-super-duper-3rd-party-lib. My control file is then: >> >> ######################## >> Source: foo >> Build-Depends: super-duper-3rd-party-lib >> ... >> >> Package: libfoo >> ... >> >> Package: libfoo-super-duper-3rd-party-lib >> ... >> ######################## >> >> Clearly only 'libfoo-super-duper-3rd-party-lib' 'Build-Depends' on >> package 'libfoo-super-duper-3rd-party-lib', which make libfoo only >> available on the limited subset of Arch for >> libfoo-super-duper-3rd-party-lib... >> >> Clearly this is an issue with availability on Arch, but I do not see >> how to express: "Use libfoo-super-duper-3rd-party-lib only if >> available" (I would then need to tweak debian/rules but this should be >> easier). > > You want an arch-specific build-dependency, like: > > super-duper-3rd-party-lib [i386 amd64]
Indeed that was simple. And I guess I need to reflect that into the 'Package: libfoo-super-duper-3rd-party-lib'/Architecture: section Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
