Created attachment 372504 [details, diff] patch for bluez-5.15.ebuild (As requested on gentoo-dev) It's possible to have an embedded system which uses mdev instead of udev, where there is a fixed range of bluetooth hardware which will be used, and where you can be sure that bluez can handle that hardware without referring to libudev's hwdb or manually switching from hid to hci mode. So I suggest that bluez should add a udev USE flag, enabled by default, and a warning for normal desktop users that disabling this flag is not a good idea. Patch attached.
Only a question, does people running this embedded systems that want to avoid udev use some kind of profile that could allow us to force +udev on everything else? I would prefer people having udev providers installed to use udev support instead of playing with it with no real gain apart of getting problems :(
(In reply to Pacho Ramos from comment #1) > Only a question, does people running this embedded systems that want to > avoid udev use some kind of profile that could allow us to force +udev on > everything else? Probably it would be better to force +udev in profiles that are guaranteed to have a udev provider - which means targets/desktop and targets/systemd.
Umm, I see udev flag is not forced commonly in other packages, then, the patch looks ok to me. Please wait a bit as I am working on this :)
+*bluez-5.16 (12 Mar 2014) + + 12 Mar 2014; Pacho Ramos <pacho@gentoo.org> +bluez-5.16.ebuild, + -bluez-5.14-r1.ebuild: + Version bump, readline is needed when client is built (#504038 by Richard Li), + make udev optional (#504324 by Alexandre Rostovtsev and Joshua Kinard), drop + old. +
