On Mon, Sep 07, 2009 at 08:56:31PM +0200, Julian Andres Klode wrote: > 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 Ah, I got it now. So, DPkg::Post-Invoke { "blah" }; is equal to DPkg::Post-Invoke:: "blah"; while DPkg::Post-Invoke:: { "blah" }; would be equal to DPkg::Post-Invoke:::: "blah"; I guess it would be good to explain this in the manpage. Probably at the place which talks about the trailing ::. A few questions remain to me: 1. Shouldn't then the "list" term be removed from the manpage? Or is Foo::Bar { "foo"; "bar"; } the construct which is generally accepted to represent a "list"? 2. In my #503481 DPkg::Post-Invoke example, why does DPkg::Post-Invoke:: { "echo 99test3"; }; get overwritten by DPkg::Post-Invoke:: { "echo 99test4"; }; To my understanding, this should expand to DPkg::Post-Invoke { { "echo 99test3"; "echo 99test4"; }; }; 3. Why does "echo 99test4" gets executed at all, it is not in the same scope as the "normal"/other DPkg::Post-Invoke commands. regards Mario -- There are two major products that come from Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson
Attachment:
signature.asc
Description: Digital signature