summaryrefslogtreecommitdiffstats
path: root/tags/l/link-to-shared-library-in-wrong-package.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/l/link-to-shared-library-in-wrong-package.tag')
-rw-r--r--tags/l/link-to-shared-library-in-wrong-package.tag19
1 files changed, 19 insertions, 0 deletions
diff --git a/tags/l/link-to-shared-library-in-wrong-package.tag b/tags/l/link-to-shared-library-in-wrong-package.tag
new file mode 100644
index 0000000..1e09451
--- /dev/null
+++ b/tags/l/link-to-shared-library-in-wrong-package.tag
@@ -0,0 +1,19 @@
+Tag: link-to-shared-library-in-wrong-package
+Severity: warning
+Check: libraries/shared/links
+Renamed-From:
+ non-dev-pkg-with-shlib-symlink
+Explanation: Although this package is not a "-dev" package, it installs a
+ "libsomething.so" symbolic link referencing the corresponding shared
+ library. When the link doesn't include the version number, it is used by
+ the linker when other programs are built against this shared library.
+ .
+ Shared libraries are supposed to place such symbolic links in their
+ respective "-dev" packages, so it is a bug to include it with the main
+ library package.
+ .
+ However, if this is a small package which includes the runtime and the
+ development libraries, this is not a bug. In the latter case, please
+ override this warning.
+See-Also:
+ debian-policy 8.4