default config file creation

Ivan Leo Murray-Smith puoti at
Wed Dec 17 10:03:55 CST 2003

> Read documentation/PACKAGING, I had it added to CVS with most ideas already
> inside on Jun 27, 1999.
I've read this. I also had a look at the recording of your speech about wine
packaging at wineconf 2002.
I've followed the indications of documentation/PACKAGING at lines 385-404,
mainly for usability.
> Feel free to copy the attached SuSE default make_fakewindows setup script I
> use and the included minimalistic wine patch to loader/main.c.
It all seems quite SuSE specific, anyway I haven't yet seen a script that works
as well as winesetuptk, and there are complaints from time to time about helper
scripts shiped with RPMs. Also a script doesn't give a user the freedom of
choosing if he wants to use a real or a fake windows partition, and doesn't allow
the user to chose where to have the fake windows partition, simply because it
can't interact with the user. Nobody seems to be currently shipping
winelauncher,and  having a scipt to start wine isn't a great idea for a beta/stable
build and ideally we want a long term solution.

Bill Medland wrote:
>I don't like the idea; I much prefer the idea of copying them from somewhere 
>in /etc, as redhat does.  The default config file in /etc can then be 
>modified so that it matches the distribution (redhat have their cd at 
>/mnt/cdrom) and it can be modified by the sysadmin
There is no need to add text files to the wine binary, but the default config
should be modified on the fly. Some computers don't have a cd or a floppy, some
have 2 cd drives, some don't use distro-standard paths, so drives should be
detected on the fly, already we have enough logs from users full of /mnt/floppy
not found and /mnt/cdrom not found, and it's not a great feature for 0.9 or 1.0. 
Winesetuptk does thit very very very well, I'm no engineer but I suppose that
something written in tcltk can be easily ported to C. A binary package (But also
a normal make install) should install configb and registry in /etc/wine or
/usr/share/doc/wine-version/samples or something like that. The user should then
start wine, that would look for $HOME/.wine, create it if necesarry, figure out
the removable media paths, create a config file on the fly, write it to $HOME/.wine,
run 'wine regedit path/to/winedefault.reg' and start normally.This does not
require a script, will create a properly working config file, and the default
configuration can be tweaked/restored with winecfg, once it's finished.


More information about the wine-devel mailing list