On Mon, Sep 07, 2009 at 06:19:54PM +0200, Mario 'BitKoenig' Holbe wrote:
> Maybe this is because it's unclear to me what is the difference between
> a "scope", a "name", and a "list" - and maybe a "value" :)
> For example, what exactly does DPkg::Post-Invoke describe? Does it have
> a type? How does it differ from DPkg::Post-Invoke:: and is it different
> from, i.e. APT::Cache-Limit or APT::Get::Assume-Yes? And if it is - how?
DPkg::Post-Invoke is an item. It can have multiple subitems which can have
name (e.g. Dpkg::Post-Invoke::Blah) or no names (e.g. Dpkg::Post-Invoke::).
There are no types. Everything is an item. An item may have a key, a
value, a parent item, and multiple subitems. An example is
'DPkg::Post-Invoke' which has the key 'Post-Invoke', an empty value
and multiple subitems which have no key but a value.
If there is a statement like 'DPkg::Post-Invoke:: "blah"' a new subitem
without a name is added to the configuration option DPkg::Post-Invoke.
The same applies to 'DPkg::Post-Invoke { "blah" }'. We create a new option
without a name below 'DPkg::Post-Invoke'. The only difference to full options
like 'APT { Architecture "blah"; }' is the missing option name. I guess
nobody would think that this would override all APT options.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Attachment:
pgpEpL5QYjrGZ.pgp
Description: PGP signature