I was wondering if it would make more sense during the compile process to take the default configuration files, config, system.reg, user.reg and userdef.reg and convert these to binary form and compile them into the wine binary itself. We could detect the lack of these files at startup and install them for the user.
Very cool idea, it would increase usability a lot. You don't really need to compile the files, you can just install them in /usr/share/doc/wine-yyyymmdd/samples or something like that and copy them to $HOME/.wine if needed. )There wouldn't be any performance loss as these files are read at startup anyway.Wine could also create a fake c drive in the users home and create a link to it it needed.
Ivan.
On Wed, Dec 17, 2003 at 10:51:42AM +0100, Ivan Leo Murray-Smith wrote:
I was wondering if it would make more sense during the compile process to take the default configuration files, config, system.reg, user.reg and userdef.reg and convert these to binary form and compile them into the wine binary itself. We could detect the lack of these files at startup and install them for the user.
Very cool idea, it would increase usability a lot. You don't really need to compile the files, you can just install them in /usr/share/doc/wine-yyyymmdd/samples or something like that and copy them to $HOME/.wine if needed. )There wouldn't be any performance loss as these files are read at startup anyway.Wine could also create a fake c drive in the users home and create a link to it it needed.
Read documentation/PACKAGING, I had it added to CVS with most ideas already inside on Jun 27, 1999.
Feel free to copy the attached SuSE default make_fakewindows setup script I use and the included minimalistic wine patch to loader/main.c.
I sill would like to avoid calling a shellscript on every wine invokation, but the instant ${HOME} -> %HOME% change was making that a bit difficult.
Ciao, Marcus
- Where should we be installing the base config files? Can we put them in the libs directory with the rest of the wine libs? I was looking at modifying documentation/Makefile.in to take care of this
- After seeing Marcus' email I realized that I completely forgot about the issue of the user not having a fake windows directory. I was thinking of breaking the fake windows code out of wineinstall and into another script. We could install this script along with the config files.
Should we be performing the config file check inside wine at startup? Ivan didn't seem to be a fan of having a script wrapper around starting wine, any other opinions?
For this config check should we do something like: if no config -> copy over default config
if windows drive doesn't exist -> create fake windows drive and setup dll/ application symlinks?
Chris
On Wednesday 17 December 2003 05:33 am, Marcus Meissner wrote:
On Wed, Dec 17, 2003 at 10:51:42AM +0100, Ivan Leo Murray-Smith wrote:
I was wondering if it would make more sense during the compile process to take the default configuration files, config, system.reg, user.reg and userdef.reg and convert these to binary form and compile them into the wine binary itself. We could detect the lack of these files at startup and install them for the user.
Very cool idea, it would increase usability a lot. You don't really need to compile the files, you can just install them in /usr/share/doc/wine-yyyymmdd/samples or something like that and copy them to $HOME/.wine if needed. )There wouldn't be any performance loss as these files are read at startup anyway.Wine could also create a fake c drive in the users home and create a link to it it needed.
Read documentation/PACKAGING, I had it added to CVS with most ideas already inside on Jun 27, 1999.
Feel free to copy the attached SuSE default make_fakewindows setup script I use and the included minimalistic wine patch to loader/main.c.
I sill would like to avoid calling a shellscript on every wine invokation, but the instant ${HOME} -> %HOME% change was making that a bit difficult.
Ciao, Marcus
-
Chris Morgan -
Ivan Leo Murray-Smith -
Marcus Meissner