You could also view the global config as the values with which to
initialise the local config when a user first uses wine. You might also
want to have a process that would refresh those values should it be
necessary to change something for all users, but that presupposes multi
user, and as I recall someone suggested that that should 1.1.
Alexandre Julliard <[EMAIL PROTECTED]> on 26-10-2000 10:29:21 PM
To: Jeremy White <[EMAIL PROTECTED]>
cc: Marcus Meissner <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
(bcc: David Goodenough/DGA/GB)
Subject: Re: Wine packaging - part 2 - what RPM/DEBs do
Jeremy White <[EMAIL PROTECTED]> writes:
> Hmm. I had not seriously considered simply adding
> an 'inherit' ability. A cursory look at the
> .winerc suggests, for most things, it would be pretty easy.
> It would make winecfg harder (or much
> harder to do well, IMO).
It would also make it much harder for users to figure out what's going
wrong (not to mention that they'll have to post both their config and
the global one to get any useful support).
> I think if we simplify the presentation
> of Wine, and discuss *only* the ~/.wine/config
> file, we'd make life easier for most Wine users.
Agreed; Wine should only try to load the user config file. If someone
really wants a global config, it is always possible to make the user
config a symlink to some central file.
--
Alexandre Julliard
[EMAIL PROTECTED]
