#8 meta-config directory standard

[Anonymous]

> how are your thoughts about naming conventions?
> I have not found docs about it.
>
> I've seen:
> /data/parsers
> /data/forms
> /data/classes
>
> should these go under /usr/share during install and be the place where
> other packages should drop their definitions too?
>
> How have you pictured multiple version handling? Do you have knowledge
> about kconf_update?
> Would the following be a reasonable approach for the meta-data?:
> Please add your thoughts.

The basic definitions that come with CFG get installed in
/cfg-definitions (wherever it lives):

/cfg-definitions/config4gnu.xml (basic config representation tree definition)
/cfg-definitions/classes/builtin.xml etc.

Eeach individual projects source directory (cvs) may have a
subdirectory named <projectname>-<version>.cfg. During installation this directiory could be copied to /cfg-definitions, for example:

/cfg-definitions/apache-1.x.cfg/
/cfg-definitions/apache-1.x.cfg/parser.xml
/cfg-definitions/apache-1.x.cfg/config.xml
/cfg-definitions/apache-1.x.cfg/xform (or better forms.xml and wizards.xml?)
/cfg-definitions/apache-1.x.cfg/virtualdomain.xform (or virtualdomain-form.xml
and virtualdomain-wizard.xml?)

Please comment on this, especially about different versions, it might not make
sense at all to have different dirs per version if versions are better
handled within the meta-config-definition itself.