I understand the value and importance of that, but I'm afraid this is
out of the Elektra scope.
Such semantics and functionality should go in a GConf or KConfig XT layer.
On 4/2/06, Joe Desbonnet <jdesbonnet(a)gmail.com> wrote:
Strings would be a sensible default in the absense of a schema, but
think you could do so much more if you had the *option* to have a
schema in the infrastructure.
For each field the schema would define the data type (string, integer,
date, ip, username, enum etc), constrains on the values (eg "must be
integer between 1-5"), a help text or hyperlink to help, and GUI hints
(eg widget preferences: pulldown menu vs radio buttons, tab groupings
So instead of a system-config-blah for each application, you just have
one system-config tool that autogenerates a GUI based on schema.