Package: libopenobex
Version: 1.3-3
Severity: wishlist
Tags: patch

Hi,

currently, no libbluetooth2-dev is available on GNU/kFreeBSD (and
that is quite "normal", I'd say, given the description and the
source of bluez-libs), so your package can't be built on this
platform. Please find attached a patch to make bluetooth-related
stuff optional for kfreebsd-*, so that your package can be built and
installed on this platform, if you feel that your package is useful
anyway. I'd think so since there's a B-D on libusb-dev, and I guess
that many PDAs can be used through an USB link. I wasn't able to
build libsyncml (my APT cache is missing some B-Ds and I'm offline
at the moment), but gnome-vfs-obexftp can be built and installed
successfully.

I'm keeping severity=wishlist since I'm not sure about the usability
of your package w/o bluetooth (but I'm quite sure it is more useful
like that than FTBFSing...).

Cheers,

-- 
Cyril Brulebois
--- libopenobex-1.3/debian/control      2007-03-26 05:20:13.618442000 +0200
+++ libopenobex-1.3/debian/control      2007-03-26 05:20:50.000000000 +0200
@@ -2,7 +2,7 @@
 Priority: optional
 Section: comm
 Maintainer: Hendrik Sattler <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 5.0.0), autotools-dev, libbluetooth2-dev, 
libusb-dev (>= 2:0.1.11), pkg-config, docbook, docbook-utils, quilt (>= 0.45), 
automake1.9, autoconf, libtool
+Build-Depends: debhelper (>= 5.0.0), autotools-dev, libbluetooth2-dev 
[!kfreebsd-i386 !kfreebsd-amd64], libusb-dev (>= 2:0.1.11), pkg-config, 
docbook, docbook-utils, quilt (>= 0.45), automake1.9, autoconf, libtool
 Standards-Version: 3.7.2.0
 
 Package: libopenobex1-dev
@@ -11,7 +11,7 @@
 Conflicts: libopenobex-dev
 Provides: libopenobex-dev
 Architecture: any
-Depends: libopenobex1 (= ${Source-Version}), libbluetooth2-dev, libusb-dev (>= 
2:0.1.11)
+Depends: libopenobex1 (= ${Source-Version}), libbluetooth2-dev [!kfreebsd-i386 
!kfreebsd-amd64], libusb-dev (>= 2:0.1.11)
 Suggests: pkg-config
 Description: OBEX protocol library - development files
  The Object Exchange protocol can best be described as binary HTTP.

Reply via email to