http://bugs.winehq.org/show_bug.cgi?id=8033
--- Comment #59 from Kai Blin blin@gmx.net 2007-10-08 14:23:19 --- As this bug keeps turning up in the bugzilla mails, I could not help to notice.
rankincj@yahoo.com, this procedure of moving away the .wine directory and creating a new one with only the application in question installed is a debugging technique. It is not out goal to force users to recreate their .wine directory on every update. However, to make debugging problems feasible, we ask people to check with a fresh .wine directory.
As a developer, I frequently run tests on a freshly installed windows machine so I can be certain I'm not seeing any artifacts created by installing other things.
Your previous posts indicate that you are going to argue that you are a user, not a developer. In this case, I can only say that this is the Wine equivalent to the advice you hear from Windows-based tech support people over and over again if you call in with problems. "Just get a clean .wine" is the same as "Please reinstall Windows". In Windows, you will not be required to do it that often anymore, but that is because Windows changes less frequently.
Now, as this is turning into some sort of a wine user experience discussion, how about we take this to some other forum more suited for a discussion like this? That will allow developers who read the bugzilla mails to focus on development, and not on people like me, who misuse the bug comments for non-bug-related posts.
-
wine-bugs＠winehq.org