The libcanberra port was not in a good state… :)
@tcberner initially wanted to depend on libcanberra-pulse in KDE Plasma 5.
I want to get rid of gtk2 dependencies as much as possible, and libcanberra-gtk was forcing gtk2 onto a lot of systems unnecessarily.
With this update,
- libcanberra-gtk2 and libcanberra-gtk3 integrations are in separate packages
- libcanberra-gtk2 is only depended on when actually used in the port
- header and vapi for gtk (which is used by any of the gtk 2/3) are in the main package, so there's no "require 2 if using 3" or vice versa situation
- well "require 3 if using 2" would kinda be acceptable, but that would be harder to do with the Uses/canberra.mk code
- libcanberra-pulse and libcanberra-gstreamer backends are in separate packages
- libcanberra-pulse actually will be used if installed
- the dependency on canberra is written with USES
- the canberra dependency is dropped from up-to-date gnome ports (e.g. some games) that have switched to only using the gsound API
- libudev won't be picked up when building outside of poudriere (it's useless here for us, the calls are for alsa soundcards I think)
References:
- https://fedora.pkgs.org/33/fedora-aarch64/libcanberra-gtk2-0.30-23.fc33.aarch64.rpm.html / https://fedora.pkgs.org/33/fedora-aarch64/libcanberra-gtk3-0.30-23.fc33.aarch64.rpm.html (gnome-settings-daemon-3.0/gtk-modules/canberra-gtk-module.desktop installed in the gtk3 one)
- https://www.archlinux.org/packages/extra/x86_64/libcanberra/ (gdm/autostart etc. not installed at all)