1deb-shlibs(5)                     dpkg suite                     deb-shlibs(5)
2
3
4

NAME

6       deb-shlibs - Debian shared library information file
7

SYNOPSIS

9       debian/shlibs, debian/binary-name.shlibs, DEBIAN/shlibs
10

DESCRIPTION

12       shlibs files map shared library names and versions (SONAMEs) to
13       dependencies suitable for a package control file.  There is one entry
14       per line. Blank lines are not allowed.  Lines beginning with a #
15       character are considered commentary, and are ignored.  All other lines
16       must have the format:
17
18           [type:] library version dependencies
19
20       The library and version fields are whitespace-delimited, but the
21       dependencies field extends to the end of the line.  The type field is
22       optional and normally not needed.
23
24       The dependencies field has the same syntax as the Depends field in a
25       binary control file, see deb-control(5).
26

SONAME FORMATS

28       The SONAME formats supported are:
29
30           name.so.version
31
32       and
33
34           name-version.so
35
36       where name is usually prefixed by lib.
37

EXAMPLES

39       The shlibs file for a typical library package, named libcrunch1, that
40       provides one library whose SONAME is libcrunch.so.1, might read
41
42        libcrunch 1 libcrunch1 (>= 1.2-1)
43
44       The dependencies must mention the most recent version of the package
45       that added new symbols to the library: in the above example, new
46       symbols were added to version 1.2 of libcrunch.  This is not the only
47       reason the dependencies might need to be tightened.
48

SEE ALSO

50       deb-control(5), dpkg-shlibdeps(1), deb-symbols(5).
51
52
53
541.21.21                           2023-02-25                     deb-shlibs(5)