Hi,
Shouldn't tools/wineprefixcreate copy a sample config file?
Right now it does all the job to create a standalone wine environment, but with no config.
I would suggest copying documentation/samples/config to tools/config, installing it at $(SRCDIR) and them just copying it during wineprefixcreate call.
I can do that if no one disagrees with the change.
Some rpms in the sourceforge does not even have the sample config file in it.
On Tue, 14 Dec 2004 09:04:17 -0200, Raul Dias raul@dias.com.br wrote:
Hi,
Shouldn't tools/wineprefixcreate copy a sample config file?
Right now it does all the job to create a standalone wine environment, but with no config.
I would suggest copying documentation/samples/config to tools/config, installing it at $(SRCDIR) and them just copying it during wineprefixcreate call.
I can do that if no one disagrees with the change.
Some rpms in the sourceforge does not even have the sample config file in it.
-- Raul Dias
We're in the process of removing the config file. As of a couple release ago (not sure how many) you can run wine without a config file, because the settings are being moved into the registry, and someday will be easily changed with winecfg.