Vitaliy Margolen schrieb:
Hello Bojan,
Thank you for opening bugs in Wine's bugzilla. It is really appreciated.
All I wanted to point out is that all installer related bugs you opened looked identical to me with exactly the same things failing.
To make a bug reproducable you have to each time remove / rename ~/.wine directory before trying to install anything else. This way you can guarantee that your Wine configuration is not contaminated by anything else.
Hi Vitali
First sorry for my aggressive reaction. I had a very bad day.
Yes, I'm a newbie in Wine, so I'll make such mistakes.
Back to the technical problems: I've made quite a mismatch in the installation of Wine and the software, mostly because I continued to install software partially with sudo. And also one application after the other. I, also as a (Java) developer, see that it's the best to clean or remove the Wine configurations (or at best the .wine directory) to see how well does Wine install on *clean* installations. This helps the developers to split basic implementation problems from those of multiple, robust, long term installation problems, which also have to be solved one day, but better *after* clean installations can be mastered.
What I find confusing is that the whole topic of running the 32-bit Wine on 64-bit machines isn't mentioned in the FAQ. Sure, such machines are still rare, and partially expensive. But they are the future. But there should be a special 64-bit topic, even for mentioning GCC bugs (even if they should be rare in 2006).
I will redo all tests with a *removed* .wine directory. Fortunaly, with an AMD X2 2.0 GHz this will work faster than with any other machine (multitasking will be not disturbed). Building Wine (after configure & make depend) with
make -j 3
takes only 10 minutes.
I've cc-ed this e-mail to wine-bugs so that everybody sees my excuses in personal and in technical affairs. I apologize mostly my personal reaction. I hope I'll become a productive tester in the Wine community.
greetings to everybody
Bojan