summaryrefslogtreecommitdiffstats
path: root/tags/u/uses-implicit-await-trigger.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/u/uses-implicit-await-trigger.tag')
-rw-r--r--tags/u/uses-implicit-await-trigger.tag19
1 files changed, 19 insertions, 0 deletions
diff --git a/tags/u/uses-implicit-await-trigger.tag b/tags/u/uses-implicit-await-trigger.tag
new file mode 100644
index 0000000..143f072
--- /dev/null
+++ b/tags/u/uses-implicit-await-trigger.tag
@@ -0,0 +1,19 @@
+Tag: uses-implicit-await-trigger
+Severity: warning
+Check: triggers
+Explanation: The listed trigger is present in the control file of the package.
+ The trigger is an <code>await</code> trigger, which may not be obvious from its name.
+ .
+ The <code>await</code> triggers place rather strong requirements on <code>dpkg</code> that often lead
+ to trigger cycles due to changes in other packages.
+ .
+ If the package does not need the guarantees that <code>dpkg</code> provides to <code>await</code>
+ triggers, please use the <code>-noawait</code> variant of the trigger. This is often
+ the case for packages that use the trigger to compile a form of cache.
+ .
+ If the package does need the guarantees provided by <code>dpkg</code>, then please
+ document the rationale in a comment above the trigger and use the
+ <code>-await</code> variant of the trigger to avoid this warning.
+See-Also:
+ deb-triggers(5),
+ Bug#774559