Am Montag 26 März 2007 04:38 schrieb Cyril Brulebois: > 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...).
How much of FreeBSD bluetooth stuff is kfreebsd-*? Where (webpage) can I read about the API? Upstream CVS has changes to support more systems and I actively help them to achieve that. However, some APIs are pretty hidden in the depth of the web and the *bsd websites are a pain to use (those badly written and incomplete manpages, they have, do not help THAT much: I need the header files). As kfreebsd-* is not part of Etch release cycle, shall we delay those changes until release or are new packages in unstable welcome? Note that libopenobex1 does not depend on bluetooth libs, only on the socket API. It's the application that need it (mainly for address conversion routines). HS
