On Sat, 22 Jul 2000, Juergen Schmied wrote:
> > > If you want to do system-wide configuration you do it in HKLM (or in
> > > /etc on UNIX).
> User values in HKCU are never system wide. Period.
> Only default values in HKU/.Default are copyed at the time of user creation.
> Leter changes in HCU/.Default are not changing HKCU
Yes, we've heard that.
> > So? The global wine.userreg (with .Default) will reside in /etc, right?
> A user.reg is per definition never system wide.
Which definition is that? There's a lot of things users are interested in
in the system-wide /etc, for example... sounds to me like local directory
paths and other default settings regarding the system (for example, mail
hosts for email programs) might be among them.
> At the moment wine is single user so the wine installation has to do it.
> This might change at some point. Then we would need a adduser in any case.
Huh? Wine, in the current state, if properly set up (does the
administrator's handbook cover this?), is 100% capable of operating
perfectly in a multiuser environment. Suddenly needing an "adduser" is a
bad, bad idea... everything should be automatic.
(How to set up Wine in a multiuser environment may not be immediately
obvious, though... but I know exactly how I'd do it... perhaps I ought to
write a guide someday?)
> No, my keys are my keys. The admin should change HKLM and not touch HKCU
> like I would not like the admin to change files in ~myuser/. He can provide a initial
> set of settings but he has not to touch my settings later. This is the way HKCU
> works. I think this is completely UNIX compatible.
So you're saying that adding keys that users may want (e.g. because of an
earlier oversight on our part, or just because the admin wants to save
himself/herself some work by fixing a common error or preconfiguring the
users' groupware clients) is out of the question?
> If the user hasn't changed its directory locations there are no keys in
> HKCU.
But HKCU is what most installers like to read. And if the "first logon"
creates the shellfolders we know about, what happens if we forgot
something and some program wants to read what we forgot? There won't be
another "first logon" to fix that...
> To fix this:
> - create default keys in HKLM
> --> WE NEED A BETTER WINE INSTALLER !!! - not every time the windows
> directory is "c:\windows" like in winedefault.reg. the current hard coded paths
> in winedefault.reg are likely a source for many problems.
What do you mean? Every time the Wine installer is used without a Windows
installation, a "c:\windows"-like! directory is created automatically by
it, it'll *always* be c:\windows! There's no problems.
And every time the Wine installer is used with a Windows installation,
winedefault.reg is *never* installed, because it's not necessary, system
registry keys already exist. In that case, what's in the winedefault.reg
will never be a source of problems either, because it doesn't matter.
> - implement right SHGetSpecialFolderLocation to read HKLM (yes I do it!)
>
> and everything would be fine.
I still have my doubts...
