Summary: | www-plugins/lightspark-0.5.4.1 should set "backend" in /etc/xdg/lightspark.conf | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | Current packages | Assignee: | Chí-Thanh Christopher Nguyễn <chithanh> |
Status: | RESOLVED FIXED | ||
Severity: | minor | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://launchpad.net/bugs/942009 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dennis Schridde
2012-02-28 18:15:43 UTC
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. |