[gentoo-dev] RFC: IUSE for system/notification sounds: sound vs. libcanberra vs. notification-sound

[gentoo-dev] RFC: IUSE for system/notification sounds: sound vs. libcanberra vs. notification-sound

[Andreas Sturmlechner]

[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]

It seems we currently have several IUSE for the same purpose, with **sound** probably having oldest mentions[1].
This came up while working on virtual/sound-theme and splitting up media-libs/libcanberra[2], and could be dealt with in the same PR.

- Should we consolidate these into a single IUSE?
- Which one?
- Any other IUSE with the same purpose not listed here?


List of current IUSE consumers below:


sound **global** use flag: - Enable sound support

sound *local* use flags:
	media-libs/libcanberra: Install x11-themes/sound-theme-freedesktop to get sounds on Gnome and Xfce.

	... others, with a different meaning:
		games-board/pysolfc: Enable sound support using dev-python/pygame
		games-roguelike/angband: Enable and install sounds
		games-rpg/drascula: Install optional audio files
		games-strategy/freeciv: Add support for sound provided by media-libs/sdl-mixer
		media-libs/libsdl: Control audio support (disable at your own risk)
		media-libs/libsdl2: Control audio support (disable at your own risk)
		net-im/toxic: [3] Enables audio calling

notification-sound *local* use flags:
	net-im/dino: notification sounds plugin

libcanberra *local* use flags:
	dev-libs/eekboard: Enable support for media-libs/libcanberra
	mail-client/claws-mail: Enable sound notification in connection with USE=notification
	net-irc/hexchat: Enable sound event support using media-libs/libcanberra
 	net-misc/eventd: Enable plugin for sounds via media-libs/libcanberra
	net-p2p/eiskaltdcpp: Enable sound notifications support over libcanberra [...]
	x11-wm/metacity: Enable sound event support using media-libs/libcanberra
	xfce-base/xfce4-settings: Enable sound event support using media-libs/libcanberra
	xfce-extra/xfce4-pulseaudio-plugin: Enable sound event support using media-libs/libcanberra



[1] https://bugs.gentoo.org/323379
[2] https://github.com/gentoo/gentoo/pull/38648
[3] Instead, net-im/toxic uses *audio-notify* for native sound notifications

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 789 bytes --]

Re: [gentoo-dev] RFC: IUSE for system/notification sounds: sound vs. libcanberra vs. notification-sound

[Michael Orlitzky]

On Fri, 2024-11-01 at 14:39 +0100, Andreas Sturmlechner wrote:
> It seems we currently have several IUSE for the same purpose, with **sound** probably having oldest mentions[1].
> This came up while working on virtual/sound-theme and splitting up media-libs/libcanberra[2], and could be dealt with in the same PR.
> 
> - Should we consolidate these into a single IUSE?
> - Which one?
> - Any other IUSE with the same purpose not listed here?
> 

Aside from the ones you've listed, there's also USE=notification used
in a few places. I kind of like USE="notification sound" for this, but
that leaves open the possibility of USE=sound doing nothing on its own.

Re: [gentoo-dev] RFC: IUSE for system/notification sounds: sound vs. libcanberra vs. notification-sound

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

On Fri, 2024-11-01 at 14:39 +0100, Andreas Sturmlechner wrote:
> It seems we currently have several IUSE for the same purpose, with **sound** probably having oldest mentions[1].
> This came up while working on virtual/sound-theme and splitting up media-libs/libcanberra[2], and could be dealt with in the same PR.
> 
> - Should we consolidate these into a single IUSE?
> - Which one?
> - Any other IUSE with the same purpose not listed here?

I think that depends on how widely you define "same purpose".

In my opinion, there's a difference between "notification sounds" (i.e.
some app makes random noise that I don't want) and "sound support
in general" (i.e. having a media player or a game with sound output).

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]