Hi Giuseppe, Robert Millan wrote:
> --- debian/control.old 2011-06-19 17:28:31.000000000 +0200 > +++ debian/control 2011-07-19 00:06:58.499069293 +0200 > @@ -3,7 +3,7 @@ > Priority: optional > Maintainer: Giuseppe Iuculano <[email protected]> > Uploaders: Florian Maier <[email protected]> > -Build-Depends: debhelper (>= 7), quilt (>= 0.40), libcam-dev [kfreebsd-i386 > kfreebsd-amd64], automake, autoconf, libcap-ng-dev [!kfreebsd-i386 > !kfreebsd-amd64 !hurd-i386 !sparc !avr32], libselinux1-dev [!kfreebsd-i386 > !kfreebsd-amd64 !hurd-i386], libusb2-dev [kfreebsd-i386 kfreebsd-amd64] > +Build-Depends: debhelper (>= 7), quilt (>= 0.40), libcam-dev [kfreebsd-any], > automake, autoconf, libcap-ng-dev [!kfreebsd-any !hurd-i386 !sparc !avr32], > libselinux1-dev [linux-any], libusb2-dev [kfreebsd-any] Quick review: * Making the libcam-dev and libusb2-dev dependencies [kfreebsd-any] indeed makes sense. * The libcap-ng-dev dependency seems to be based on (old) toolchain bugs. Packages-arch-specific now says !kfreebsd-amd64 !kfreebsd-i386 !hurd-i386 for that package, and the sparc build failure was worked around about a year ago. Since the package uses linux/capability.h, in an ideal world linux-any !avr32 would be appropriate, and in today's world (because mixed positive and negative architecture specifiers aren't allowed): !kfreebsd-any !hurd-any !avr32 * libselinux is indeed still Linux-specific. To be consistent with P-a-s, I suppose !kfreebsd-any !hurd-any would be clearest. Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
