Re: BlueZ Status in Fedora.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The whole reason why the bluez5 package was proposed as a separate one was so that we didn't have to cater for every desktop under the sun that's included in Fedora.

bluez5 would conflict with bluez. If you had both MATE and GNOME installed, you wouldn't be able to upgrade to the latest version of GNOME as it would require bluez5 and the installed MATE bluez (4.x). That was the main idea, and would have avoided breaking all the desktops.

At the end of the day, if somebody pushes bluez 5.x in the old bluez package, and it ends up breaking other things, I'm fine with it as well. Other desktops will need to follow up and make sure they get the porting in updates or admit that they don't have the manpower to keep up with that particular feature.

----- Original Message -----
> Am Tue, 13 Aug 2013 08:34:53 +0000
> schrieb devel-request@xxxxxxxxxxxxxxxxxxxxxxx:
> 
> > Message: 13
> > Date: Tue, 13 Aug 2013 01:03:20 +0200
> > From: Kalev Lember <kalevlember@xxxxxxxxx>
> > To: devel@xxxxxxxxxxxxxxxxxxxxxxx
> > Subject: Re: BlueZ Status in Fedora.
> > Message-ID: <520969B8.1030601@xxxxxxxxx>
> > Content-Type: text/plain; charset=UTF-8
> > 
> > On 08/02/2013 10:15 AM, Jaroslav Reznik wrote:
> > > Let me know - I'd like to have this one as a Change if it's going to F20
> > 
> > I have been coordinating with various people and looks like all teams
> > are go. NetworkManager and PulseAudio changes are slightly lagging
> > behind, but it's probably best if we move forward and try to integrate
> > everything together in Rawhide before branching F20.
> > 
> > I've cleaned up the feature page and marked it as ready for wrangler:
> > 
> > https://fedoraproject.org/wiki/Changes/Bluez5
> > 
> > Sorry it's coming so late -- I didn't feel comfortable submitting it
> > earlier knowing how much of the upstream development was still in flux.
> > 
> mate-bluetooth doesn't support bluez5, and upstream doesn't have started to
> port it.
> I don't expect that is is ready before f20 alpha or beata.
> So it would be very nice not to push bluez5 into f20.
> Also Cristofph Wickert asked me to clean up runtime dependencies for
> mate-bluetooth to avoid that xfce/lxde user don't have to be install to many
> mate packages if they want to use mate-bluetooth.
> It seems there is a plan that xfce/lxde also want to be use mate-bluetooth.
> (maybe)
> 
> So f21 is Ok as goal, but f20 is definitely to early for mate.
> 
> Thank you
> Wolfgang
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux