bluez (4.x) and bluez-5

[Dennis Veatch]

These modules are not compatible in the sense of one will over write the 
following files;

Conflicting file(s) for modules bluez-5, bluez:
/usr/lib/libbluetooth.so.3
/usr/include/bluetooth/hci.h
/usr/include/bluetooth/hidp.h
/usr/bin/hcitool
/usr/include/bluetooth/sco.h
/usr/bin/gatttool
/usr/bin/l2ping
/usr/bin/ciptool
/usr/bin/rfcomm
/usr/include/bluetooth/bluetooth.h
/usr/lib/libbluetooth.so
/usr/include/bluetooth/hci_lib.h
/usr/include/bluetooth/sdp_lib.h
/usr/lib/systemd/system/bluetooth.service
/usr/include/bluetooth/bnep.h
/usr/include/bluetooth/cmtp.h
/usr/include/bluetooth/l2cap.h
/usr/bin/l2test
/usr/lib/cups/backend/bluetooth
/usr/bin/rctest
/usr/bin/sdptool
/usr/include/bluetooth/sdp.h
/usr/include/bluetooth/mgmt.h
/usr/lib/pkgconfig/bluez.pc
/usr/include/bluetooth/rfcomm.h

Bluez-5 has a compatibility layer via the use of --enable-library and by 
default said switch is enabled in the BUILD. 

Unless someone has a specific reason bluez-4 should be kept *and* willing to 
spend the effort to resolve the above conflicts. I recommend we remove bluez-4 
from moonbase.

Dennis