Ove Kaaven wrote:
> On Sat, 22 Jul 2000, David Elliott wrote:
>
> > If you want to do system-wide configuration you do it in HKLM (or in
> > /etc on UNIX).
>
> So? The global wine.userreg (with .Default) will reside in /etc, right?
>
> > You can write a shell script to export HKEY_USERS\.Default and then sed it to
> > HKEY_USERS\username and then import it.
>
> No plans. That has "user-unfriendly" spelled all over it. It's okay if a
> system administrator has to do some work to make a wine installation work
> for everyone, but there should not be extra setup work per user!
>
> > I understand your argument that this is stupid, but that is how it is supposed
> > to work.
>
> No, it isn't. Windows was never supposed to work on top of the Unix
> security and filesystem model, and Wine was never supposed to be developed
> in the way it has, so don't give me that.
>
> > Also, you shouldn't absolutely NEED a setting in HKEY_CURRENT_USER to
> > run a program.
>
> But you do, as has been shown time and time again. Installers need Shell
> Folders and probably other stuff that we figure out later and have to add
> to winedefault.reg... wouldn't it be nice if all system administrators
> could retro-add the new keys we figured out we need, without going through
> every single user's account?
Okay, I do see your arguments..
As I understand it, Wine currently has a global registry and a user registry. The
global registry gets loaded first, then user settings are loaded on top of that.
Any modifications will be written to the user registry and if possible the global
registry (which will probably only be possible if you have write access to it, for
instance a "wine" account or something like that maybe).
I would suggest maybe having an HKEY_USERS\.Wine which will load into
HKEY_CURRENT_USER first, and then the users settings will be loaded on top of that.
This seems to be what you want to do with the .Default key. Shell folders and
other stuff can be in here that will be the same for all users. I would suggest
H:\.wine\* instead of C:\WINDOWS\*
The .Default key should function exactly as it does in Windows (like an
/etc/skel). That way it would be more compatible with the way Windows does things.
This would bring the best of both worlds: sysadmins could retro-add new keys simply
by changing stuff in the .Wine subkey. Applications expecting .Default to function
exactly like Windows are still happy.
-Dave
