Commit ec2ebca2 authored by Raphaël Hertzog's avatar Raphaël Hertzog

Update triggers documentation to match reality

- The list of triggers is in the second parameter and not in the third.
- The --verbose and --query options for dpkg-trigger have never been
parent 7b561513
......@@ -185,7 +185,7 @@ away redundant processing.
In that case, where an interested package has more than one trigger
and wants to process them differently, the list of triggers can be can
be examined in a shell script like this:
case " $3 " in
case " $2 " in
*" trigger-name-a "*) process-trigger-a ;;
Generally each trigger name should be tested for separately, as the
......@@ -338,12 +338,8 @@ A trigger may be activated explicitly with:
dpkg-trigger [--by-package <package>] <name-of-trigger>
dpkg-trigger --no-await <name-of-trigger>
The --verbose and --query options will show which packages were
interested and what the current activation state is, on stdout in
human- and machine-readable (untranslated) format. Without any
options there will be no output to stdout, and none to stderr unless
There will be no output to stdout, and none to stderr unless
dpkg-trigger is unable to make a record of the trigger activation.
With --query no trigger is activated.
NB that in the case of a file trigger the name of the trigger is
needed, not the name of a file which would match the trigger.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment