Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


If it's ok with everyone I'm going to include cleaned bluetooth headers,
from android, in the source tree to avoid the need for installing a library
which isn't actually linked or used. (Headers viewable
http://gitorious.org/0xdroid/system_bluetooth/trees/59ca0be6dc8ef3f30f8f863d8fb805a55bf12fe5/bluez-clean-headers/bluetooth
).


Sorry for replying late, but I am a bit unsure about this. Is it really a
good idea to have these "cleaned" header copies in our tree? I mean, one
more package to depend on (bluez-devel in the SUSE case, libbluetooth-dev
in Debian), what's the big deal with that? If some of the distro versions
we want to support don't have any such, we just need to make the Bluetooth
remote server code optional with a configure switch and some ifdefs, right?

--tml

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.