Mon Mar 9 07:14:45 PDT 2009
I don't want to add this to the Swfdec 0.8 branch, as patches there should be
as small as possible and not include new features (I've been getting questions
from distros about every patch). So I suggest you keep it as a custom patch in
the OpenBSD ports system.
I'm however not really sure how I want to handle audio backends in Swfdec after
the experiences I've had with OSS and Pulse. For everyone reading this, the
short version of the problem is:
a) There are no core Swfdec developers using the specific backend, so it is not
exposed to the same amount of testing.
b) People download Swfdec and compile it with their preferred audio backend.
When using it, it crashes, so they conclude Swfdec sucks and don't bother
I don't want to lose users (or even distros, as those users in b) have been
distro packagers) just because they don't know that the audio backends have
different levels of support and assume the experience with their chosen audio
backend is an indication of overall Swfdec quality.
On the other hand it's a good idea to support as many audio backends as
So I'm torn between adding audio backends and suggesting that distros maintain
their own backend.
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Swfdec