Differences between revisions 2 and 3
Revision 2 as of 2004-03-01 13:40:24
Size: 729
Editor: anonymous
Comment:
Revision 3 as of 2004-03-01 14:13:29
Size: 849
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
With config4gnu in debian however the cons can be eliminated and new possibilities arise. With the config4gnu config representation and manipulation framework in debian however the cons can be eliminated and new possibilities arise.
Line 8: Line 8:
Full flexibility and authority of /etc is maintainted, flexibility even increased and a API and several frondends (comandline, GUI etc.) to all config files and formats are provided. Full flexibility and authority of /etc is maintainted. Flexibility is even increased, a API and several frondends (comandline, GUI etc.) to all config files and formats are provided without hardcoded specifics!

Meta-config definitions do the trick
.

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

This mix of different textformats 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, a API and several frondends (comandline, GUI etc.) to all config files and formats are provided without hardcoded specifics!

Meta-config definitions do the trick.

Check out the webpage: http://config4gnu.sourceforge.net/

"Points of Integration config4gnu in debian" (or better integrate debian into config4gnu ?):