Rather than hardcode the ebuild to only use notification-daemon, please provide a || list of choices, including notification-daemon-xfce and xfce4-notifyd. I tested Blueman with xfce4-notify, and it works just fine. There's absolutely no change in functionality. :) The reason why I ask this is because installing xfce4-notify !blocks other notification daemons, of course, as they all use the same libnotify. Unfortunately, that means that world cannot be properly updated anymore because Blueman wants only notification-daemon, which has the same !blocks as all the other notifyd packages. So if you switch it to || -type depends, that should alleviate the problem. Thanks!
http://blueman-project.org/downloads.html says that blueman depend on "notification-daemon or any other libnotify compatible engine", so maybe we need change dependency from notification-daemon to libnotify?
Created attachment 212300 [details, diff] patch for blueman-1.02 ebuild notification-daemon -> libnotify
Created attachment 212302 [details, diff] patch for blueman-1.10 ebuild same, but for 1.10
Nope. As far as I know you still need something that's running libnotify, not just libnotify itself. Besides, notify-python already pulls in the libnotify dep. What we want is a || to allow any of a few choices. This is what should go in the ebuilds, to replace notification-daemon: || ( x11-misc/notification-daemon x11-misc/xfce4-notifyd )
Created attachment 215362 [details] blueman-1.02.ebuild (In reply to comment #4) > This is what should go in the ebuilds, to replace notification-daemon: > > || ( x11-misc/notification-daemon x11-misc/xfce4-notifyd ) but libnotify already have this dep... nevertheless, i've made new version of ebuild
Created attachment 215364 [details] blueman-1.10.ebuild same for blueman-1.10
Created attachment 215366 [details, diff] blueman-1.02.ebuild.patch patch for easy review
Created attachment 215368 [details, diff] blueman-1.10.ebuild.patch and for blueman-1.10
libnotify should be the correct dep.
solved with version bump to 1.21. Dropped dep on a notification-daemon completely since package doesn't check for it and notify-python pulls them in anyway.
