On debian-devel-announce, Wichert Akkerman <wichert@soil.nl> wrote: > 2.4. Configuration Management > ----------------------------- > > Yes, DPKGv2 hopes to incorporate internal configuration functions. > This coincides with the debian-admintool effort. Since packages and > configuration are so closely tied together, the merger will benefit > both sides. Configuration management will be developed in the core > library to be used in conjunction with the other functionality and > should prove an integral part of future advances in packaging by > allowing for non-interactive installs, centralized repositories for > data, network administration and more. > > Several key things will be involved in the config functions. First, it > will handle all of the persistent data storage for the package system > (db modules). Data storage will be configurable with modules (ie, db2, > plain, LDAP...). It will also evolve into a network management > interface, which could allow for remote frontend interfaces. Use ACAP -- Application Configuration Access Protocol. It is documented in RFC 2244 Here is a taster: Abstract The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. The data store model is designed to allow a client relatively simple access to interesting data, to allow new information to be easily added without server re-configuration, and to promote the use of both standardized data and custom or proprietary data. Key features include "inheritance" which can be used to manage default values for configuration settings and access control lists which allow interesting personal information to be shared and group information to be restricted. -- I consume, therefore I am
Attachment:
pgpb3ArScuShC.pgp
Description: PGP signature