Re: A standard package for config files is needed

[tmoran@acm.org]

> ...  I usually used Emacs to edit the files, rather than bother with
> a spreadsheet or DB program.  But some people did prefer the database
> program, and having in that format allows people to do DB queries on

  I'm starting to wonder if everyone is thinking of the same thing when
they use the term "configuration data".  Or are we all on different
wavelengths here.  I myself am thinking of persistent information that
is specific to a particular user and installation, but not a particular
execution (eg, not an individual document in the case of a word
processing program).  I also include information that is needed for
installation and un-installation on a machine, independent of the
particular user.  That's a pretty broad definition, including file
lists and file paths and such text as, for instance, standard
signatures.  My definition also includes settings of flags and
semi-constants, including structured constants like color palettes or
fonts.  Those are typically not textual and understanding them requires
at least some understanding of the inner workings of the program.  Does
that jibe with what the term is meaning to other folks?