BlueZ Status in Fedora.

[Dan Williams]

On Thu, 2013-08-01 at 18:36 +0100, Peter Robinson wrote:
> On Thu, Aug 1, 2013 at 6:14 PM, Tomasz Torcz <tomek at pipebreaker.pl> wrote:
> > On Thu, Aug 01, 2013 at 07:05:39PM +0200, Stefan Held wrote:
> >> What exactly is holding the Updates back in Fedora?
> >> Is there a reason for excluding the 5.x Series?
> >
> >
> >   See https://fedoraproject.org/wiki/Changes/Bluez5
> > and the thread starting at https://lists.fedoraproject.org/pipermail/devel/2013-May/182355.html
> 
> I was kind of expecting this would have landed by now though, Bastien
> will be @ GUADEC this week so not sure if he'll respond quickly

For the NetworkManager side, porting to Bluez5 requires a couple things
yet to finish:

1) DUN support: bluez5 makes this incredibly difficult because the DUN
serial channel is no longer a kernel device and thus can't be used with
pppd, can only be seen by one process, thus we pretty much have to cut
Bluez5 out of the DUN path entirely.  That's being worked on slowly.

2) a behavior change in NetworkManager to show all PAN/DUN capable
devices immediately, not just ones that have been configured during
pairing.  This requires some updates to the GUI apps and some additional
changes to NetworkManager to prompt the user to configure the device
upon first-use, instead of at pair-time.

Dan