On Fre, 2013-08-16 at 15:06 -0400, Greg Freemyer wrote:
To me, jumping to Bluez 5 exclusively for 13.1 just feels like its too late in the development cycle. To do that right would surely require another couple milestone releases.
Good thing, though, is we would not be alone: F20 does it as well (and they do have KDE in there as well.. incl. fixes). Ubuntu did not make the switch yet, but have GNOME 3.10 in the repositories for Saucy. So I'd guess bluetooth either does not work or they reverted patches to try to keep bluez4 alive.
<brainstorming> By using conflicting "Recommends:" statements, couldn't both Gnome and KDE be installable, but only one would have Bluetooth support?
'Conflicting Recommends'? you can recommend packages that do not exist; rpm does not care; only zypper / yast does... and if packages do not exist, they are skipped... after all, it's only recommendations.
Or, how hard would be to change the Bluez 5 namespace to not conflict. Then both could co-exist? <\brainstorming>
IF, then I'd rather recommend doing this on the obsolete base (moving bluez4 out of the way). The biggest issue, imho, is that it's runtime failures only, not buildtime... so anything relying on the bluez4 dbus api simply drips over... Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org