On Wed, 2005-11-23 at 00:26 -0500, Michael Gilbert wrote: > if alsa is to be the primary Debian audio backend in the future (not > sure if this is on the agenda in the Etch time-frame or not), then > shouldn't the code 'just work' if someone is using alsa.
No. The code should "just work" if you properly follow its recommendations. If you choose to forge out on your own, you take risks. One of those risks is that the software won't work and I'll ignore your "bug". > hence, the > dependency on GConf or python-gnome2 or whatever should be met to > support backend autodection. This is exactly the case recommends were designed for; I suggest you reread Policy 7.2. > either that or the backend should be a > selectable gui preference, but i think GConf is the simpler (more > automated) route. > > please do not insult my intelligence. i'm obviously smart enough to > figure out what the problem was and fix it. i was reporting it here > to make sure that you were aware of it in the hope that you could fix > it so other (more novice) users won't have to deal with it. There wasn't any insult implied. If I had wanted to do that I would've asked why you were reporting a duplicate, addressed to my satisfaction in an upload a week ago. -- Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
