Audacious plugins includes a libnotify plugin which currently auto-detects the library. The ebuild should use the 'libnotify' USE flag to enable and disable the libnotify support. ./configure --help: [...] --disable-notify disable libnotify plugin (default=enabled) [...]
update, audacious-plugins-1.2.1
This is on hold until a working version of libnotify is released. Current versions will cause Audacious to segfault on exit and have a nasty D-Bus problem that I haven't been able to pin down. You are free to try it yourself, but I will not add the USE-flag until I can explicitly depend on a libnotify without obvious bugs.
Well, you should add at least a --disable-notify, because now audacious-plugins configure script automatically enables the plugin if libnotify is available on the system.
(In reply to comment #2) > This is on hold until a working version of libnotify is released. Current > versions will cause Audacious to segfault on exit and have a nasty D-Bus > problem that I haven't been able to pin down. > You are free to try it yourself, but I will not add the USE-flag until I can > explicitly depend on a libnotify without obvious bugs. > On my system works very well. media-sound/audacious-1.2.0_rc3 media-plugins/audacious-plugins-1.2.1 sys-apps/dbus-0.91 dev-libs/dbus-glib-0.71 x11-libs/libnotify-0.4.3 x11-misc/notification-daemon-0.3.6 the ebuild needs the libnotify useflag to pull in required deps.
Very well, libnotify USE-flag added to audacious-plugins-1.2.2-r1; note that you have been warned about instability that I can not solve as the problem is in libnotify. Keep this in mind when filing/assigning bugs.
