/etc/xdg/lightspark.conf contains backend=pulseaudio by default, even if USE=-pulseaudio. In this case audio will simply and silently not work. I suggest adding this to src_install(): use pulseaudio || sed -e 's/backend = pulseaudio/backend = sdl/' -i "${D}"/etc/xdg/lightspark.conf Upstream bug is [1], and they might also decide to adjust the default config, in which case the abovementioned sed would become obsolete. [1] https://bugs.launchpad.net/lightspark/+bug/942009 Reproducible: Always
Upstream decided for WONTFIX and points at the packager to adjust the config file.
That's not great indeed. Allowing to specify comma-delimited list of backends which are tried in order, or an option like backend=auto / default_backend that falls back to another one if necessary would be more elegant. But it's only a one-time configuration which is necessary presently. So I am unsure whether the current situation is better or forcing dispatch-conf/etc-update run after USE flag changes.
(In reply to comment #2) > That's not great indeed. Allowing to specify comma-delimited list of > backends which are tried in order, or an option like backend=auto / > default_backend that falls back to another one if necessary would be more > elegant. Feel free to suggest that to upstream. What I asked for was setting the backend via cmake based on the value of AUDIO_BACKEND. > But it's only a one-time configuration which is necessary presently. So I am > unsure whether the current situation is better or forcing > dispatch-conf/etc-update run after USE flag changes. The primary issue IMO is that the user usually does not know about that config file (and it is also unexpected for a plugin to be configurable in this manner) and hence is just confused why his audio does not work.
Fixed in CVS.