Hi,
>>"Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> Installation-time Configuration
Wichert> The configuration space
Wichert> =======================
Wichert> The configuration space is the realm in which all
Wichert> configuration information is stores. This space is divided
Wichert> into different sections in the same way a filesystem is. The
Wichert> toplevel-hiearchy is for package: each package has it's own
Wichert> configuration data in a folder of the root. Packages which
Wichert> share a common purpose may use a shared folder, preferable
Wichert> with the same as as a shared (virtual) packagename (for
Wichert> eaxmple, both mutt and elm could use mail-reader, strn and
Wichert> nn could use news-reader). Within a folder the configuration
Wichert> items (variables) are stored. Each variable has associated
Wichert> with it one or more tags (meta-information). These are used
Wichert> to detect if a variable has been changed by the user or not,
Wichert> in much the same manner as md5sums are used to detect
Wichert> changed conffiles.
Hmm. I wonder. Is there areason for a flat heirarchy? Could
deeper nesting have value? For example, there could be a "folder"
called MUA (or something), and all mail user agents go there, a
higher level value (/top/mua/mailhosthostname) can be over ridden by
/top/mua/vm/mailhostname); it allows a group of packages to share a
default.
I can see value in deeper nesting of configuration
variables. There is more structure this way; but that also entails
more work creating the structure.
manoj
--
A physicist is an atoms way of knowing about atoms. George Wald
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
