Eli Wapniarski wrote:
Stop trying to integrate or force integration of everything into
I disagree. It's important for components to work together.
And there is of yet, still no official support for pulse under wine.
But there is the WinePulse project which is what we're shipping.
If you encounter bugs with it, you need to
And the reason upstream WINE refuses to merge the patch is because they want
to rewrite the whole sound system and they don't want any new backends
until that happens, no matter how important those new backends are. :-/ It
has nothing to do with the quality of the backend.
Why should a soundserver interfere with networking?
I don't know. But there's certainly an explanation.
Right now the defacto standard Linux soundserver is alsa.
No, the de-facto standard is PulseAudio now. We aren't the only ones
shipping it as the default, at least Ubuntu and Mandriva ship it too.
It's not possible to have apps only support hardware ALSA in a PulseAudio
environment, they'll not work (because PulseAudio needs the sound device).
The problem with WINE's ALSA backend is that it needs mmap and thus won't
work with the PulseAudio ALSA plugin.
You can try the ESD backend (wine-esd), which uses PulseAudio's ESD
compatibility layer (pulseaudio-esound-compat).
Please lets do what we can to not go the Redhat 8 route again.
Do you have anything against Bluecurve? I still use it. :-)