summaryrefslogtreecommitdiffstats
path: root/tags/b/build-depends-on-build-essential-package-without-using-version.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/b/build-depends-on-build-essential-package-without-using-version.tag')
-rw-r--r--tags/b/build-depends-on-build-essential-package-without-using-version.tag13
1 files changed, 13 insertions, 0 deletions
diff --git a/tags/b/build-depends-on-build-essential-package-without-using-version.tag b/tags/b/build-depends-on-build-essential-package-without-using-version.tag
new file mode 100644
index 0000000..a8a3b79
--- /dev/null
+++ b/tags/b/build-depends-on-build-essential-package-without-using-version.tag
@@ -0,0 +1,13 @@
+Tag: build-depends-on-build-essential-package-without-using-version
+Severity: error
+Check: fields/package-relations
+See-Also: debian-policy 4.2
+Explanation: The package declares a build-depends on a build essential package
+ without using a versioned depends. Packages do not have to depend on any
+ package included in build-essential. It is the responsibility of anyone
+ building packages to have all build-essential packages installed. The
+ only reason for an explicit dependency on a package included in
+ build-essential is if a particular version of that package is required,
+ in which case the dependency should include the version.
+Renamed-From:
+ depends-on-build-essential-package-without-using-version