Fwd: apt.conf syntax clarification

[Dmitriy Matrosov <sgf.dma@gmail.com>]

---------- Forwarded message ----------
From: Dmitriy Matrosov <sgf.dma@gmail.com>
Date: 2011/12/17
Subject: Re: apt.conf syntax clarification
To: David Kalnischkies <kalnischkies+debian@gmail.com>

Sorry, i forget to fix an address. This is copy to maillist.

2011/12/16 David Kalnischkies <kalnischkies+debian@gmail.com>:
>
> Yeap, expect "List is a group of nameless options" - List is a group of
> options - they CAN have names (and with these names, you can even override
> list items), just read again what you quoted as [4] - it says exactly that.
>
> Configoption not only stores a (optional) name and a (optional) value but
> also other Configoptions - specifically two: The next config option on the
> same level (=silbing) and the next config option one level below (=child).

Thanks for the answer! So, record like

Acquire
{
   Order { "gz"; "lzma"; "bz2"; };
};

will result in following config options tree

o (n=Acquire v=NUL) --> NUL
|
v
o (n=Order v=NUL) --> NUL
|
v
o (n=NUL v="gz") --> o (n=NUL v="lzma") --> o (n=NUL v="bz2")
|                    |                      |
v                    v                      v
NUL                 NUL                   NUL

where n is name, v is value, horizontal arrow is "sibling" pointer
and vertical arrow is "child" pointer. Am i right, now?

> List, Scope and co are just describing different syntax ways to create
> the same think: A configoption-tree. In the end a list is just a scope in
> which you have 'forgotten' to set an explicit name.

But list has name, doesn't it? Or do you mean 'forgotten' to set an
explicit name for list elements ("child" options)?

--
  Dmitriy Matrosov