From 29e3fc2e05b59a7e13913a263a1e22d40cbc9918 Mon Sep 17 00:00:00 2001 From: Russ Allbery Date: Sun, 12 Aug 2012 16:32:35 -0700 Subject: [PATCH] Reflect the common case in the shlibs example --- policy.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/policy.sgml b/policy.sgml index 050c688..3c863dc 100644 --- a/policy.sgml +++ b/policy.sgml @@ -6796,10 +6796,10 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)

In our example, if the last change to the zlib1g package that could change behavior for a client of that - library was in version 1:1.2.3.3.dfsg-2, then + library was in version 1:1.2.3.3.dfsg-1, then the shlibs entry for this library could say: - libz 1 zlib1g (>= 1:1.2.3.3.dfsg-2~) + libz 1 zlib1g (>= 1:1.2.3.3.dfsg) This version restriction must be new enough that any binary built against the current version of the library will work @@ -6811,7 +6811,7 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) As zlib1g also provides a udeb containing the shared library, there would also be a second line: - udeb: libz 1 zlib1g-udeb (>= 1:1.2.3.3.dfsg-2~) + udeb: libz 1 zlib1g-udeb (>= 1:1.2.3.3.dfsg)

-- 2.39.2