A lighter-weight approach seems more promising: encapsulate most of the
config-file specific knowledge in simple script wrappers that can be
controlled by a declarative description of the configuration you want to
achieve and the logical interdependencies between them. This is what
puppet does, and why I find it very attractive.
Hummm, never heard about puppet. Seems interesting.
The problem I see with this approach is the additional layer that manages the configuration files syntax. And again: ALL configuration files can be represented by an hierarchy of key/value pairs. They are different because they received a considerable amount of syntax fat to make them look nicer to your human eyes. And what puppet seems to do is try to work with this fat.
Elektra completely removes that fat and reduces the configuration parameters to what they really are: key/value pairs.
Avi
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
