>And I try to set up the correct winedbg path in
>the registry, since I think the default path in winedefault.reg doesn't
>do much good if you don't run from the wine source directory (and who
>does that?)
(I do ;-)
>(Just one issue I wondered about... wineinstall currently only installs
>winedefault.reg if a previous Windows install is not detected, but
>certain keys, like the winedbg stuff, should perhaps be installed
>anyway...
>perhaps they should be separated out of winedefault.reg and somewhere
>else, so wineinstall can install that even if an existing Windows is
>found?)
in all cases, we should report to the user, when installing a key:
- if it's a new key (either created by the deltas in wine source code,
or a key he/she -deliberately- destroyed
- if it's an existing key, with a different value (meaning that either
user's modified it, or wine developers did change it). in both cases,
user should be asked what he/she likes to do (this would mean adding
some documentation to the key itself)
we definitively need something more robust than we have now
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
