Changeset d0da969c

Timestamp:

05/27/2023 10:07:58 PM (11 months ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

12.0, 12.0-rc1, 12.1, 12.1-rc1, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc

Children:

360371a

Parents:

55a29cc

Message:

Reword library conflict paragraph.

File:

• chapter08/pkgmgt.xml (modified) (1 diff)

chapter08/pkgmgt.xml

@@ -86 +86 @@
       </listitem>
 
-      <listitem><para>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
-      <filename class='libraryfile'>libfoo.so.2</filename> and
+      <listitem><para>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 <filename class='libraryfile'>libfoo.so.2</filename> and
       <filename class='libraryfile'>libbar.so.1</filename>, while the latter
-      links to
-      <filename class='libraryfile'>libfoo.so.3</filename> 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 <filename class='libraryfile'>libfoo.so.3</filename>), 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.
       </para></listitem>