Difference between revisions of "How Should An Application Honour Configuration Files"

Latest revision as of 06:47, 28 February 2013

The following list contains the run down an application should follow when working with configuration information:

Each application has sane defaults and initializes all variables accordingly.
If a global configuration file exists (/etc/xxxxx), the content of the configuration file takes precedence.
If a private configuration file exists (~/.xxxxx), the content of the private configuration takes precedence.
If commandline options exist, the commandline option take precedence.
If an input form for configuraiton information exist, it gets filled with the vars up to this point.
If an input form for configuration information exist, the user gets can either be asked if the private configuration file should be overwritten with the new information, or it can be done automatically.

Revision as of 20:51, 27 February 2013 (view source) Marie.o (Talk \| contribs) (Notes on using configuration files, commandline options etc.)		Latest revision as of 06:47, 28 February 2013 (view source) Marie.o (Talk \| contribs) m
Line 1:		Line 1:
−	The following list contains the run down an application should follow when working with configuration ~~issues~~:	+	The following list contains the run down an application should follow when working with configuration information:

	# Each application has sane defaults and initializes all variables accordingly.		# Each application has sane defaults and initializes all variables accordingly.