Differences between revisions 11 and 12
Revision 11 as of 2006-03-27 17:31:53
Size: 1117
Comment: Typos, readability.
Revision 12 as of 2006-05-03 12:50:17
Size: 3783
Comment: list of features
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:

"Points of Integration for config4gnu in debian":

 * DebConf
 * DebianInstaller
 * DebianDesktop
 * DebianControlCenter


== Wishlist for "the perfect configuration modifier" ==

The configuration (modifier) system should...

- remove any need to manually copy customisations to new config files during upgrades or to alternatively not get updated config files.

- ease to (re)do/revisit config manipulation scripts with every new package
(update). (Today maintainer scripts need to provide the complete funtionality
from parser, validation, ..., logic. Therefore incomplete sets of options and
"managed by debconf" (don't touch or loose debconf functionality) sections
are implemented.)


- provide sytem configs with cascading defaults:

Defaults with different config levels:

0. software defaults (compiled in, not saved in config files)

1. system settings (explicity saved in /etc/*)

compiled from different sets of defaults

 - A. distro defaults (saved in some config system /usr/share/... dir)

 - B. customized defaults (Custom Debian Distributions) (/usr/share/...)

 - C. more customized defaults (Organisations etc.) (/var/share/...)

 - ...

and overridden by possible explicit (different) admin settings done in /etc (results in /etc/* to have an offset from the default resulting from A.B.C...)

2. settings for user groups (see debian package desktop-profiles)
  
3. user settings (explicity saved in ~/.*)


- still allow all levels to be networked by importing /usr/bin, some /usr/share/...,
some /var/share/..., /etc and /home dirs repectively.


- frontends and backends separtated from the core

- provide seamless adjustment of settings on every level for the frontends

- provide central reference settings and linking (to keep track of and update
multiple redundant occurances in various places upon changes (i.e. hostname,
IPs etc.)

- be able to provide possible options/values, comments and help.

- separate config-system and config-system-configuration (fileformat/info
about the software it configures. According to workflow of package
maintainer, package-config-manipulator maintainer, config-system maintainer,
customisation-maintainer, etc.)

- not save config state outside of the configured software's original config
storage.

- understand the fileformat and not alter formating when applying changes.

- have a modular config-system-configuration, so that it can be upgraded with
files that can be part of the software packages of the distributions or from
other sources.

- have the possibility to draw-in necessary packages if the user wants to
configure some not-installed functions. (interaction with package manager)






== Tracking Tools ==
Line 17: Line 102:

"Points of Integration config4gnu in debian":

 * DebConf
 * DebianInstaller
 * DebianDesktop
 * DebianControlCenter

The standard way system wide configuration data is kept in unices is by various different config files under the /etc directory.

This mix of different text formats is unlikely to change given various pros and cons.

With the config4gnu config representation and manipulation framework in debian, however, the cons can be eliminated and new possibilities arise. Full flexibility and authority of /etc is maintainted. Flexibility is even increased; an API and several front ends (comand line, GUI, etc.) to all config files and formats are provided without hardcoded specifics.

Meta-config definitions do the trick.

Check out the webpage: http://freedesktop.org/Software/CFG

"Points of Integration for config4gnu in debian":

Wishlist for "the perfect configuration modifier"

The configuration (modifier) system should...

- remove any need to manually copy customisations to new config files during upgrades or to alternatively not get updated config files.

- ease to (re)do/revisit config manipulation scripts with every new package (update). (Today maintainer scripts need to provide the complete funtionality from parser, validation, ..., logic. Therefore incomplete sets of options and "managed by debconf" (don't touch or loose debconf functionality) sections are implemented.)

- provide sytem configs with cascading defaults:

Defaults with different config levels:

0. software defaults (compiled in, not saved in config files)

1. system settings (explicity saved in /etc/*)

compiled from different sets of defaults

  • - A. distro defaults (saved in some config system /usr/share/... dir) - B. customized defaults (Custom Debian Distributions) (/usr/share/...) - C. more customized defaults (Organisations etc.) (/var/share/...) - ...

and overridden by possible explicit (different) admin settings done in /etc (results in /etc/* to have an offset from the default resulting from A.B.C...)

2. settings for user groups (see debian package desktop-profiles)

3. user settings (explicity saved in ~/.*)

- still allow all levels to be networked by importing /usr/bin, some /usr/share/..., some /var/share/..., /etc and /home dirs repectively.

- frontends and backends separtated from the core

- provide seamless adjustment of settings on every level for the frontends

- provide central reference settings and linking (to keep track of and update multiple redundant occurances in various places upon changes (i.e. hostname, IPs etc.)

- be able to provide possible options/values, comments and help.

- separate config-system and config-system-configuration (fileformat/info about the software it configures. According to workflow of package maintainer, package-config-manipulator maintainer, config-system maintainer, customisation-maintainer, etc.)

- not save config state outside of the configured software's original config storage.

- understand the fileformat and not alter formating when applying changes.

- have a modular config-system-configuration, so that it can be upgraded with files that can be part of the software packages of the distributions or from other sources.

- have the possibility to draw-in necessary packages if the user wants to configure some not-installed functions. (interaction with package manager)

Tracking Tools

If you want to keep track of your configuration changes, either for yourself or because you are administering a Debian box with someone else, have a look at the following packages:

  • changetrack (needs perl)
  • filetraq (shell)
  • diffmon