> Why not? Do install it. Do all user based config in ~/.winerc.
> For this "inherting .INI files" would be good, where ~/.winerc
> only contain the user changes, all others are inherited from the
> global .winerc.
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). That is, you'd want winecfg
to show you all drive mappings, with a color coding
for ones in your ~/.winerc and ones inherited
from the global wine conf.
However, I think I want to push back on this one.
I love a global conf file as much as the next guy,
but what does it really buy us? Admittedly,
a global conf file is a prerequisite to graceful
multi user Wine, but do we really know people who
do multi user Wine?
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.
So, I guess the retort to 'Why not?' is 'Why?'.
Just my $0.02.
Jer
p.s. In case the use of ~/.wine/config is
confusing to some people, it is my
understanding that is what ~/.winerc
is going to become in the near future,
and that it will be in the new registry format.
