Am Tue, 13 Aug 2013 12:00:01 +0000 schrieb devel-request@lists.fedoraproject.org:
Message: 4 Date: Tue, 13 Aug 2013 11:26:05 +0200 From: Kalev Lember kalevlember@gmail.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: Re: BlueZ Status in Fedora. Message-ID: 5209FBAD.50108@gmail.com Content-Type: text/plain; charset=UTF-8
On 08/13/2013 11:11 AM, Rave it wrote:
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)
Can you use gnome-bluetooth instead?
I mean, mate-bluetooth is just a fork on an older version of gnome-bluetooth. It probably made sense to use the fork when MATE was based on gtk2 (because you can't mix gtk2 and gtk3 librarires), but now that MATE has switched to gtk3, you guys should be able to switch back to gnome-bluetooth proper.
In general this is a possibility for the future (for fedora and upstream), because GTK3 is a development goal in mate upstream. But we have currently no fixed release date for MATE-1.8. And i'm pretty shure it doen't comes before next year. So GTK3 in MATE is a feature for f21/22. Other probs are: 1. gnome-bluetooth upstream has removed the fallback icon for autostart in session,.......no systray icon in other DE than gnome itself. 2. if gnome revert this change in upstream 'OnlyShowIn=MATE" needs to be added. 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate.
On 08/13/2013 02:28 PM, Rave it wrote:
Other probs are:
- gnome-bluetooth upstream has removed the fallback icon for autostart in session,.......no systray icon in other DE than gnome itself.
- if gnome revert this change in upstream 'OnlyShowIn=MATE" needs to be added.
- Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate.
I discussed this with raveit65 on IRC and we found a way forward with this.
The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13... when GNOME stopped shipping the fallback mode.
However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth.
Anyone interested in teaming up with raveit65 to create a separate package for this?
This package might also be useful for XFCE/LXDE.
In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code.
On Tue, Aug 13, 2013 at 6:44 AM, Kalev Lember kalevlember@gmail.com wrote:
On 08/13/2013 02:28 PM, Rave it wrote:
Other probs are:
- gnome-bluetooth upstream has removed the fallback icon for autostart in session,.......no systray icon in other DE than gnome itself.
- if gnome revert this change in upstream 'OnlyShowIn=MATE" needs to be added.
- Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate.
I discussed this with raveit65 on IRC and we found a way forward with this.
The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13... when GNOME stopped shipping the fallback mode.
However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth.
Anyone interested in teaming up with raveit65 to create a separate package for this?
This package might also be useful for XFCE/LXDE.
In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code.
-- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Could we reverse this commit? Everyone wins.
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Dan
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Lars
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.seipel@gmail.com wrote:
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Not so simple as reverting a commit. Must discuss with upstream.
Dan
On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal dan.mashal@gmail.com wrote:
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.seipel@gmail.com wrote:
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Not so simple as reverting a commit. Must discuss with upstream.
Dan
Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate:
"3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate."
The whole point of forking to be dependant on gnome upstream as little as possible.
Dan
On Thu, 2013-08-15 at 15:10 -0700, Dan Mashal wrote:
On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal dan.mashal@gmail.com wrote:
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.seipel@gmail.com wrote:
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Not so simple as reverting a commit. Must discuss with upstream.
Dan
Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate:
"3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate."
The whole point of forking to be dependant on gnome upstream as little as possible.
If you want to be independent of GNOME upstream, you need the resources to keep up to date with upstream changes in a timely fashion. It's not going to work for Fedora to delay moving to new upstream releases of major components for entire release cycles because MATE didn't have the resources to be ready for the change.
We've go the resources.
An entire DE doesn't appear out of nowhere.
Just trying to determine how to proceed.
Dan Sent from my Verizon Wireless BlackBerry
-----Original Message----- From: Adam Williamson awilliam@redhat.com Sender: devel-bounces@lists.fedoraproject.org Date: Fri, 16 Aug 2013 17:19:27 To: Development discussions related to Fedoradevel@lists.fedoraproject.org Reply-To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: Re: BlueZ Status in Fedora.
On Thu, 2013-08-15 at 15:10 -0700, Dan Mashal wrote:
On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal dan.mashal@gmail.com wrote:
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.seipel@gmail.com wrote:
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Not so simple as reverting a commit. Must discuss with upstream.
Dan
Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate:
"3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate."
The whole point of forking to be dependant on gnome upstream as little as possible.
If you want to be independent of GNOME upstream, you need the resources to keep up to date with upstream changes in a timely fashion. It's not going to work for Fedora to delay moving to new upstream releases of major components for entire release cycles because MATE didn't have the resources to be ready for the change.
On Thu, 2013-08-15 at 15:04 -0700, Dan Mashal wrote:
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.seipel@gmail.com wrote:
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time.
Reforking? And then wait until the bitrot sets in again? ;-)
Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed?
Not so simple as reverting a commit. Must discuss with upstream.
Please make it a separate package.
On 08/13/2013 09:44 AM, Kalev Lember wrote:
On 08/13/2013 02:28 PM, Rave it wrote:
Other probs are:
- gnome-bluetooth upstream has removed the fallback icon for autostart in session,.......no systray icon in other DE than gnome itself.
- if gnome revert this change in upstream 'OnlyShowIn=MATE" needs to be added.
- Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate.
I discussed this with raveit65 on IRC and we found a way forward with this.
The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13... when GNOME stopped shipping the fallback mode.
However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth.
Anyone interested in teaming up with raveit65 to create a separate package for this?
This package might also be useful for XFCE/LXDE.
In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code.
Will the bluez-compat be killed in this move?
JBG
On 08/17/2013 01:47 AM, "Jóhann B. Guðmundsson" wrote:
Will the bluez-compat be killed in this move?
Yes, already gone in the rawhide package:
http://pkgs.fedoraproject.org/cgit/bluez.git/commit/?id=e321c716dddf55724776...
https://bugzilla.redhat.com/show_bug.cgi?id=754523
-
Adam Williamson -
Dan Mashal -
Jóhann B. Guðmundsson -
Kalev Lember -
Lars Seipel -
Matthias Clasen -
Rave it