Wine staging tree

[Sebastian Lackner]

On 02.10.2014 17:29, Rosanne DiMesio wrote:
> On Thu, 02 Oct 2014 16:57:24 +0200
> Michael Müller <michael at fds-team.de> wrote:
> 
> 
>> We
>> may consider adding a similar warning like Pulseaudio if this is going
>> to be a problem.
>>
> 
> Please do so, because it is going to be a problem. The reality is users don't always tell us they are using an unsupported build; many of them don't really know what they are using. Those of us who provide user support need a way to immediately identify your build so we can direct your users to your support channels. Asking everyone to run wine --patches (which is what we would have to do without such a warning) is unreasonable.
> 
> I do realize the Fedora situation is not your fault. But IMO, it illustrates why you do need to put the warning in your build. You have no way of stopping other packagers from doing the same.
> 
> 

I've just added a patch to show such a warning similar to winepulse and modified the wine version string by appending '(Compholio)', as suggested by Austin. It will be part of Wine-Compholio >= 1.7.28. Hopefully this will calm down all people who are concerned about invalid bug reports.

Nevertheless, from my own experience of working on specific bugs, I don't think it will have any significant effect: Users will _never_ be able to provide fully detailed information to ensure the issue can be reproduced. Users without any visible sign of a patched version might use PlayOnLinux (no changed --version), might use a self-build version with missing dependencies or wrong gcc version, might use a huge amount of winetricks recipes, all applied on top of each other, might use Ubuntu Wine (containing wine-multimedia, which is _more_ than just a minimal patchset for PulseAudio support), might have broken drivers, ...

Regards,
Sebastian