From: Maarten t. H. <ma...@tr...> - 2003-06-20 22:57:35
|
On Friday 20 June 2003 21:21, Manuel Bilderbeek wrote: > Maarten ter Huurne wrote: > > Good point. The system-wide settings.xml was introduced to give system > > admins a way to set reasonable default settings for their users. So we > > assume that someone will be altering the file. Then it doesn't make sense > > to overwrite it with every release. Also, it is redundant to keep default > > both in the code and in the installed settings.xml. So I propose not to > > install a settings.xml file. > > The advantage is that the default settings can be determined by the > system administrator without recompiling the program. I think we should > keep the global settings.xml. I'm not saying we shouldn't keep the feature, I only think it is better not to install the settings.xml file. In the HOWTO we can explain how an admin can take the settings.xml file from his home dir and promote that to the system default. Actually, system-wide config files should be in /etc instead of /opt, maybe that's causing part of the confusion. I don't think any program's install procedure overwrites files in /etc. > Note that Laurens uses the Windows version > of openMSX. I don't know how the install procedure is arranged there. The problem he describes occurs on Linux too. The difference is that on Linux, the user is more likely to edit ~/.openMSX/share/settings.xml rather than /opt/openMSX/share/settings.xml. > Anyway, the global settings file should be overwritten, but not the > local one in the user's home dir, IMO. If the global settings file is made by the system administrator, then why should we overwrite it? Bye, Maarten |