default config file creation

[Chris Morgan]

Trading off configurability with usability seems fine to 
me.  I doubt you'd hear much complaining about the default 
configuration not being correct and users wanting to edit 
it.  In either case if the same can be accomplished 
without including the config files in the binary then that 
of course is preferrable as long as these files are picked 
up by the package maintainers.  The goal is to solve both 
the lack of config files for binary installs, fixed by the 
patches that Che has in his rpm package and Marcus has for 
Suse, and for users that run 'make install' but never 
create config files.

Chris



On Wed, 17 Dec 2003 17:11:44 +0100
  "Ivan Leo Murray-Smith" <puoti at inwind.it> wrote:
>>The less modification to the install process the better. 
>  >If there was a single location the files could be 
>>installed to that would work for all distros I think this 
>>is the route to head in.
>You can install the files anywhere, as long as the 
>location isn't already used
>for something else, /etc/wine could do.
>Also, compiling the files means nobody could change the 
>default config without
>recompiling wine, that sound short of weird.
>
>Ivan.
>
>
>
>