summaryrefslogtreecommitdiffstats
path: root/tags/s/shared-library-lacks-version.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/s/shared-library-lacks-version.tag')
-rw-r--r--tags/s/shared-library-lacks-version.tag24
1 files changed, 24 insertions, 0 deletions
diff --git a/tags/s/shared-library-lacks-version.tag b/tags/s/shared-library-lacks-version.tag
new file mode 100644
index 0000000..aebb8c6
--- /dev/null
+++ b/tags/s/shared-library-lacks-version.tag
@@ -0,0 +1,24 @@
+Tag: shared-library-lacks-version
+Severity: warning
+Check: debian/shlibs
+Renamed-From:
+ shlib-without-versioned-soname
+Explanation: The listed shared library in a public library directory has an
+ SONAME that does not contain any versioning information, either after the
+ <code>.so</code> or before it and set off by a hyphen. It cannot therefore
+ be represented in the shlibs system, and if linked by binaries its
+ interface cannot safely change. There is no backward-compatible way to
+ migrate programs linked against it to a new ABI.
+ .
+ Normally, this means the shared library is a private library for a
+ particular application and is not meant for general use. Policy
+ recommends that such libraries be installed in a subdirectory of
+ <code>/usr/lib</code> rather than in a public shared library directory.
+ .
+ To view the SONAME of a shared library, run <code>readelf -d</code> on the
+ shared library and look for the tag of type SONAME.
+ .
+ There are some special stub libraries or special-purpose shared objects
+ for which an ABI version is not meaningful. If this is one of those
+ cases, please add an override.
+See-Also: debian-policy 10.2, debian-policy 8.6