[Pkg-xfce-devel] Bug#631573: Bug#631573: plasma-widgets-workspace: Forces removal of xfce4-notifyd

Yves-Alexis Perez corsac at debian.org
Sat Jun 25 23:32:35 UTC 2011

reassign 631573 plasma-widgets-workspace
On sam., 2011-06-25 at 18:26 +0200, Sune Vuorela wrote:
> On Saturday 25 June 2011 18:02:29 Yves-Alexis Perez wrote:
> > Then one solution is to fix plasma-widget-workspace to work under Xfce.
> > I assume that means not using xfdesktop4 and running the whole plasmoids
> > stuff but Sune would know better than me.
> It would require runnig a Plasma workspace (desktop or netbook shell)

Ok, so that's a solution.
> > I don't know anything about KDE dependencies but I'd find that weird to
> > have a hard dependency on a notification daemon. 
> It is basically built in (thru plugins) to the workspace.

> > xfce4-notifyd provides/conflicts with notification-daemon package
> > because they both
> > ship /usr/share/dbus-1/services/org.freedesktop.Notifications.service.
> > Is there a reason why plasma-widgets-workspace does it? 
> plasma-widgets-workspace contains the stuff that make a plasma shell implement 
> the org.freedesktop.Notifications interface.

Well, that's not the (only) reason why xfce4-notifyd does it. The first
reason is the dbus service. If you think a virtual package is needed (a
“real” virtual) maybe you should ask for it, but adding a provides
without shipping the actual dbus service looks to me like an abuse.
> Some packages depends or recommends 'notification-daemon' because they require 
> or can use that dbus interface. 

Which is not provided by plasma-widgets-workspace afaict.
> Currently it is provided by
> notify-osd
> plasma-widgets-workspace
> xfce4-notifyd
> and the following packages has a 'install by default' relationship with 
> notification-daemon:
> $ grep-dctrl -FDepends -FRecommends notification-daemon -sPackage 
> /var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_*i386*Packages
> Package: blueman
> Package: claws-mail-multi-notifier
> Package: deluge-gtk
> Package: evolution-plugins
> Package: gajim
> Package: gnome-power-manager
> Package: guake
> Package: gufw
> Package: libdesktop-notify-perl
> Package: libnotify1
> Package: listen
> Package: mail-notification
> Package: network-manager-gnome
> Package: libnotify0.4-cil
> Package: prelude-notify
> Package: quodlibet-plugins
> Package: rhythmbox
> Package: service-discovery-applet
> Package: update-notifier
> Package: wammu
> Package: xfce4-goodies
> and I can't see why most of these packages should pull in notify-osd or xfce4-
> notifyd when run by users of one of the KDE Workspaces

Because notification-daemon is more about the dbus service than
something else. At least that's how I interpreted it when I added the
conflicts/replaces on xfce4-notifyd.
> I'm not sure of the good way out of this, but I really think that the full 
> xfce stack sholud be coinstallable with the default stack by KDE, without 
> pulling in eachothers components.

Well, xfce4-notifyd conflict is against the *real* notification-daemon
package. Not against plasma-widgets-workspace, and indeed they might be
co-installable. But you get it because of the provides, that's all. So
I'm reassigning because of that.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-xfce-devel/attachments/20110626/c73613ac/attachment.pgp>

More information about the Pkg-xfce-devel mailing list