On 16/08/13 16:39, Dominique Leuenberger a.k.a. Dimstar wrote: > > Quoting Matthias Clasen <[email protected]>: > >> Hey, >> >> the 3.9.90 release is coming up next week - it marks the beginning of >> our freezes, so this is a good time to review the blocker bug list >> again. After my first post earlier this week, I got some >> contributions, so the list is well-populated now. >> NetworkManager >> ------------------------ >> >> 701078 Port NM to BlueZ 5 > > IMHO, this is very late to happen 'just before RC' (3.9.90 is on Aug 20) with > a > full ABI/API freeze. > > As of now, distros did not do the switch to BlueZ5 as > * It can not be parallel installed with BlueZ4 > * It is not backwards compatible > * So far, only very few components know how to use it > > Of course, at one point we will have to bite the bullet... but 'just before > RC' > for such a drastic change is, in my opinion, not the best way; > > And I don't think NM is even the only piece in the GNOME stack affected; from > a > quick glance, I can see at least also: > * GVFS (backend; can probably be disabled). > * gnokii (seems those Nokia phones just don't die!) > * gnome-phone-manager (mostly obsolete I guess). > > And stuff outside of the reach of GNOME: > * PulseAudio (has a bluetooth module) > * qemu (bring BT support to VMs) > > This all would be no issue if the variants could co-exist of course :(
The NM patches add a configure switch for bluez 5. If you don't pass it, bluez 4 support is compiled. As for the other modules, if you want 3.10 with bluez 4: gnome-shell: you need to revert a trivial patch gnome-control-center: likewise gnome-user-share: stay at 3.8. the only changes after 3.8.3 are bluez 5 support so you won't miss anything. gnome-bluetooth: stay at 3.8. 3.9/3.10 drop support for bluez 4 and change the libgnome-bluetooth ABI. NM: don't pass --enable-bluez5. Cheers, Emilio _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
