[augeas-devel] Policy for variable node names without a value

[David Lutterkort]

On Wed, 2010-10-27 at 23:09 +0200, Raphaël Pinson wrote:
> In xinetd.aug, services are mapped using key instead of a "service" label,
> just as in inetd.aug currently. The result is that the tree can look like
> this (this part is from the test module for xinetd.aug):
> 
>   { "#comment" = "default: off" }
>   { "#comment" = "description: The CVS service can record the history of
> your source" }
>   { "#comment" = "files. CVS stores all the versions of a file in a single"
> }
>   { "#comment" = "file in a clever way that only stores the differences" }
>   { "#comment" = "between versions." }
>   { "cvspserver"
>       { "disable" = "yes" }
>       { "port" = "2401" }
>       { "socket_type" = "stream" }
>       { "protocol" = "tcp" }
>       { "wait" = "no" }
>       { "user" = "root" }
>       { "passenv" { "value" = "PATH" } }
>       { "server" = "/usr/bin/cvs" }
>       { "env" { "del" } { "value" = "HOME=/var/cvs" } }
>       { "server_args"
>           { "value" = "-f" }
>           { "value" = "--allow-root=/var/cvs" }
>           { "value" = "pserver" } }
>       { "#comment" = "bind                    = 127.0.0.1" }
>       { "log_on_failure" { "add" } { "value" = "HOST" } } }
> 
> 
> I'm not a big fan of this, because you end up with nodes that have variable
> names, and no value. In that case, the node name is "cvspserver" and there
> is no value associated to the node.

Yes, you are absolutely right - I should have used a fixed label there.
Do you have a patch ?

David