http://bugs.winehq.org/show_bug.cgi?id=1486
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2004-09-09 00:56 ------- Samuel Herzog writes:
-The user wants a working application. -The user wants to have the functions in the mainmenu. -The user does not know what a TestCases is. -The user is not interested in TestCases.
So you urge to sacrifice Wine architecture fineness, scalability, perspective of future growth just for the few users to be able to run few applications?
So, you mean Wine should be designed for minority of the world? You mean all the world should work just for few people? You are despotic person then. :-)
Wine should not, IMHO. Wines license doesn't restrict you from applying any patch in your box/at your home. So, if you are using CVS to compile wine, you can do this even automatically (by adding some lines to cvs-update script once). I have just did this:
--- ../cvs_update 2004-09-09 08:51:58.000000000 +0200 +++ ../cvs_update_w_patch 2004-09-09 08:50:25.000000000 +0200 @@ -55,10 +55,18 @@ export CVSROOT=:pserver:cvs@cvs.winehq.com:/home/wine #export CVSROOT=:pserver:cvs@rhlx01.fht-esslingen.de:/home/wine push_to_CVS_dir + # unapplying the patch: + cd wine + w3m -dump "http://www.winehq.com/hypermail/wine-patches/2004/09/0074.html" | patch -Rp0 --forward + cd .. + # updating: if [[ $1 == "" ]]; then cvs update -PAd; else cvs update -PdD "$1"; fi + # applying the patch: + cd wine + w3m -dump "http://www.winehq.com/hypermail/wine-patches/2004/09/0074.html" | patch -p0 pop_dir }
and it works. It may be better idea to move the reversing/forwarind patch game to simple separate script. This would let you control several patches at once and you will be easily able to do it by hand also.
Wine is supposed not to restrict you from being free, and you vote for restricting Wine. Boo! ;-)