http://bugs.winehq.org/show_bug.cgi?id=6971
--- Comment #320 from Manuel Soukup linuxuser-sky@gmx.de 2010-02-08 08:46:34 --- My 2 cents to the hack vs fix flamewar.
I know as a dev (I develop in python) it is important to have clean code without hacks and workarounds but this bug affects many applications and most of them are games.
And gamers want to play their games.
When this means to patch wine source so we can play our game than lets do it!
I would say:
Lets patch us __our__ wine version with hacks/patches wahtever so we can play or FIX it in the svn and stop moaning.
This is actually the idea behind open source everyone can submit a patch to make the application work again for him.
I know that there was a discussion that this bug is fixed in a new Xorg release or something but till this is here and the Distros are using it we can patch our versions.
I dont see the point as long as the patches are not pasted into svn there is no problem in the svn code with hacks and stuff and this is actually only a place where ppl submit their solution to a problem. If devs read this thread and think omg another hack they have 2 choices:
1. Get angry because of a patch that is not in svn and is not seen in the actual code
2. See that others try to help other people with a problem in __their__ wine version and be glad to see the open source spirit around. Then close this thread and continue to work on clean wine code
just my thoughts