libcanberra is a new blessed dependency of GNOME. It provides a library for portable event sound API, that implements the Freedesktop.org sound theme specification. It can use either pulseaudio, alsa, gstreamer or a dummy null driver to play themed sounds with that priority order of output methods (pulseaudio can do glitch-free and positional event sounds, alsa doesn't possibly loose some utilized hardware features, gstreamer supports resampling on systems where ALSA and pulse is not available).
libcanberra will be a hard dependency on epiphany and (maybe optional in) gnome-control-center and replaces the dreaded esound daemon in all remaining GNOME usages in GNOME-2.24.
x11-themes/sound-theme-freedesktop is a default fallback sound theme for use by sound theme supporting libraries and applications, currently only through libcanberra.
As these packages will become the replacement of esound, gnome-audio and system sounds in GNOME-2.24, please give them some keyword love.
You can test by installing both (libcanberra with USE=gtk) and using canberra-gtk-play --id="<sound themed name>", where "sound themed name" is one from the documented themable sounds at http://0pointer.de/public/sound-naming-spec.html
However sound-theme-freedesktop supports only a subset of those, so basically you can test with any .ogg file that sound-theme-freedesktop ships as the ID, dropping the .ogg suffix. So canberra-gtk-play --id="desktop-login" should play the default desktop login sound.
You can also test by running a gtk+ application, such as gtk-demo, with the gtk+ sound events module provided by libcanberra[gtk], as follows on a graphical terminal:
... with that various operations, such as clicking on buttons, minimizing, maximizing, etc, should make sounds.
Hopefully all arches that have keywords on gnome-audio, epiphany and/or gnome-control-center can add the keywords (the gtk+ event sounds can be useful to everyone, GNOME users or not). This is a requirement for a full GNOME-2.24.
bug 240093 tells that if you use pulseaudio then event sounds with hyphens won't be played until bug 240093 is solved. So you can test with something that doesn't have a hyphen or not use pulseaudio - I don't think keywording should be blocked by a pulseaudio case here, as this is just with one of the drivers, and we are talking only of ~arch, not stabilization.
Please also re-keyword www-client/epiphany-184.108.40.206 (or newer if available by then) when there's libcanberra. Epiphany-2.24 ebuild currently hard depends on libcanberra, but if really necessary we can make it optional, even though libcanberra is really tiny (89KB in total for main library, gtk+ library and a good backend sound driver)
also www-client/epiphany-extensions-2.24.0 please, as it depends on >=epiphany-2.24.0
for epiphany and epiphany-extensions I of course mean rekeywording if you have keywords on previous versions - if not, I don't object adding keywords regardless though ;)
(In reply to comment #1)
> bug 240093 tells that if you use pulseaudio then event sounds with hyphens
> won't be played until bug 240093 is solved.
This particular bug was introduced in pulseaudio-0.9.12. Pulseaudio-0.9.11-r2 works, as does pulseaudio-0.9.13.
ppc/ppc64, this is a notification that you just lost your keyword on >=xchat-gnome-0.24 because of this bug.
~ppc64. i guess we are in a position to ~xchat-gnome but that also has a hard dep on a newer gcc that we have stable.
I already did this for arm/sh
@bsd, can you give us a status on what you intend to keyword and what not ? TIA.
(In reply to comment #12)
> @bsd, can you give us a status on what you intend to keyword and what not ?
libcanberra and the sound theme have been done a while ago, epiphany requires xul 1.9, bug #275807
thanks for the update. Updating summary and dependencies.
As per Comment #13, nothing for sound@ here.
As discussed with BSD, xulrunner-1.9 issues are not going to be fixed anytime soon => nuke keywords for now by removing 2.24.3 versions of epiphany & epiphany-extensions (bug 324953)