summaryrefslogtreecommitdiffstats
path: root/tags/d/debconf-is-not-a-registry.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/d/debconf-is-not-a-registry.tag')
-rw-r--r--tags/d/debconf-is-not-a-registry.tag17
1 files changed, 17 insertions, 0 deletions
diff --git a/tags/d/debconf-is-not-a-registry.tag b/tags/d/debconf-is-not-a-registry.tag
new file mode 100644
index 0000000..6fdbf4b
--- /dev/null
+++ b/tags/d/debconf-is-not-a-registry.tag
@@ -0,0 +1,17 @@
+Tag: debconf-is-not-a-registry
+Severity: warning
+Check: debian/debconf
+Explanation: In the Unix tradition, Debian packages should have human-readable and
+ human-editable configuration files. This package uses debconf commands
+ outside its maintainer scripts, which often indicates that it is taking
+ configuration information directly from the debconf database. Typically,
+ packages should use debconf-supplied information to generate
+ configuration files, and -- to avoid losing configuration information on
+ upgrades -- should parse these configuration files in the <code>config</code>
+ script if it is necessary to ask the user for changes.
+ .
+ Some standalone programs may legitimately use debconf to prompt the user
+ for questions. If you maintain a package containing such a program,
+ please install an override. Other exceptions to this check include
+ configuration scripts called from the package's post-installation script.
+See-Also: developer-reference 6.5.1, debconf-devel(7)