http://bugs.winehq.org/show_bug.cgi?id=10495
--- Comment #186 from Ben Klein shacklein@gmail.com 2009-10-10 19:49:19 --- (In reply to comment #184)
(In reply to comment #183)
You are aware that Wine cannot just support what is "common" or popular?
I think I'm used to be aware that the use case for Wine is exactly to support what's "common" and popular - that's the whole point of supporting Windows applications under different OS', isn't it?
See bug 10000. Your argument means that Wine should drop support for OSX, Solaris, Freebsd, etc.
API design has *everything* to do with code, because the code implements the API design.
That way around, sure - sorry for being unclear. Just old code, that is simply scrapped when the API redesign comes, should in no way influence either the API design or the new code written from scratch.
But the old code is not scrapped, it has to be ported to the new API design. Hence the reluctance in accepting *any* new audio drivers until the framework is fixed.
The only thing people are asking is to get a driver in vanilla Wine that allows them to use Wine well with current desktop distros until that golden age of new Wine Audio dawns.
winealsa and dmix. Done. It's not Wine's fault that distros like Ubuntu make it difficult to get what really *is* the standard audio solution on Linux working.