From: Guillem Jover Date: Tue, 8 Apr 2008 03:31:52 +0000 (+0300) Subject: doc: Fix wrong dpkg trigger related option names X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=de995070a648eadd33dc6321a94c19c596149bd6;p=dpkg doc: Fix wrong dpkg trigger related option names --- diff --git a/ChangeLog b/ChangeLog index ade8a057..5971afce 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2008-04-08 Guillem Jover + + * doc/triggers.txt: Fix wrong dpkg trigger related option names. + 2008-04-08 Guillem Jover * doc/triggers.txt: Move parts of the document into proper man pages. diff --git a/doc/triggers.txt b/doc/triggers.txt index f71c038d..915e8e74 100644 --- a/doc/triggers.txt +++ b/doc/triggers.txt @@ -364,14 +364,13 @@ package in `config-failed' or `installed'. Note that automatic package management tools which call dpkg (like apt and aptitude) should not attempt to configure individual packages in state `triggers-pending' (or indeed `triggers-awaited') with dpkg ---triggers ... or dpkg --suppress-triggers --configure -..., or similar approaches. This might defeat dpkg's trigger -cycle detection. +--triggers-only ... or dpkg --no-triggers --configure ..., +or similar approaches. This might defeat dpkg's trigger cycle detection. A package management tool which will run dpkg --configure --pending at -the end may use --suppress-triggers on its other dpkg runs. This -would be more efficient as it allows more aggressive deferral (and -hence more unification) of trigger processing. +the end may use --no-triggers on its other dpkg runs. This would be +more efficient as it allows more aggressive deferral (and hence more +unification) of trigger processing. Error handling