Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 406197 - www-plugins/lightspark-0.5.4.1 should set "backend" in /etc/xdg/lightspark.conf
Summary: www-plugins/lightspark-0.5.4.1 should set "backend" in /etc/xdg/lightspark.conf
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Chí-Thanh Christopher Nguyễn
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-28 18:15 UTC by Dennis Schridde
Modified: 2012-02-29 19:08 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2012-02-28 18:15:43 UTC
/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
Comment 1 Dennis Schridde 2012-02-28 21:23:09 UTC
Upstream decided for WONTFIX and points at the packager to adjust the config file.
Comment 2 Chí-Thanh Christopher Nguyễn gentoo-dev 2012-02-28 21:32:50 UTC
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.
Comment 3 Dennis Schridde 2012-02-28 22:05:28 UTC
(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.
Comment 4 Chí-Thanh Christopher Nguyễn gentoo-dev 2012-02-29 19:08:11 UTC
Fixed in CVS.