http://bugs.winehq.org/show_bug.cgi?id=8033
--- Comment #40 from rankincj@yahoo.com 2007-10-07 08:01:53 --- (In reply to comment #39)
What missing registry entries? Are you copying over the app installation from a Windows install?
No, this box is Windows-free! The point is that installing applications sometimes adds important keys into the .reg files, and some games refuse to run unless these keys are present.
What mandatory registry entries are you talking about? Registry entries are created *only* when you run wineprefixcreate, so you have to remove the old .wine and generate a new .wine.
No, applications install their own registry entries too... (Obviously). And that's "mandatory" as in "Wine blithely assumes that these registry keys exist, and will core-dump if they do not.".
This also gets rid of any cruft from installing other apps that may interfere with the bug
One man's "cruft" is another man's "crucial installation entry"...
(installation and uninstallation in Wine is not complete and that's another reason why this is the policy).
As I suspected, you are completely neglecting what happens when people upgrade Wine. And *everyone* upgrades Wine, and *no-one* reinstalls all their applications each time either.
$ mv .wine .wine-save $ wineprefixcreate $ test app $ mv .wine-save .wine
voila! Your old apps are back...
Yes, but along with the *old* .reg files, which presumably don't contain the latest "mandatory / Wine-will-crash-unless-they-are-present" keys. So how is that helpful? And trying to test my app doing what you've described above doesn't work *precisely* because all the "cruft" is missing from the newly-created .wine directory, and so the game flat refuses to run.
So, please tell me: How are all we millions of Wine users supposed to update the .reg files in our .wine directories with the latest "must-have" keys, whenever we upgrade to the latest version of Wine?
-
wine-bugs＠winehq.org