From d0da969c43b3963ae20a88884e2fa2f2503172d5 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sat, 27 May 2023 17:07:58 -0500 Subject: [PATCH] Reword library conflict paragraph. --- chapter08/pkgmgt.xml | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index a5c64f3f6..f64778e71 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -85,20 +85,18 @@ libraries until all the dependent packages have been recompiled. - If a package is (directly or indirectly) linked to - both the old and new names of one shared library (for example, the - package links to both - libfoo.so.2 and + If a package is (directly or indirectly) linked to both + the old and new versions of a shared library (for example, the package + links to both libfoo.so.2 and libbar.so.1, while the latter - links to - libfoo.so.3 in turn), the - package may malfunction because the different names of the shared - library provide incompatible functions with same symbol names. This - can be caused by recompiling some (but not all) packages linked to the - old shared library name after the package providing the shared library - is upgraded. To avoid the issue, it's recommended to recompile every - package linked to a shared library of which the name has been changed - during an upgrade as soon as possible, in their dependency order. + links to libfoo.so.3), the + package may malfunction because the different revisions of the shared + library present conflicting locations for some symbol names. This can be + caused by recompiling some, but not all, of the packages linked to the + old shared library after the package providing the shared library is + upgraded. To avoid the issue, users will need to rebuild every package + linked to a shared library with an updated revision (e.g. libfoo.so.2 to + libfoo.so.3) as soon as possible. If a package containing a shared library is updated,