On 23/01/14 21:19, Dan Williams wrote: > On Thu, 2014-01-23 at 14:17 -0600, Dan Williams wrote: >> On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote: >>> On 23/01/14 19:58, Frank Murphy wrote: >>>> On Thu, 23 Jan 2014 19:53:19 +0100 [...snip...] >>> Might even be a worse conflict for other users, depending on installed >>> packages. I believe there's no way around re-compiling NetworkManager, >>> pulseaudio and other GNOME and KDE packages depending on bluez. >> >> NM only uses bluez via the D-Bus interface, so if you force install >> bluez4, NM will still work and should even handle the change at runtime. >> And then you'll get DUN back too :) > > Clarification: I actually don't mean runtime. NM must be restarted to > notice the change from bluez4 <-> bluez5, but it does not need to be > recompiled. The DBus interface with bluez5 have changed too. <http://www.bluez.org/bluez-5-api-introduction-and-porting-guide/> Does NM support both bluez NM APIs? -- kind regards, David SOmmerseth -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
