diff options
| author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2023-05-27 17:07:58 -0500 |
|---|---|---|
| committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2023-05-27 17:07:58 -0500 |
| commit | d0da969c43b3963ae20a88884e2fa2f2503172d5 (patch) | |
| tree | 189a5765842fbf8f75b2a8d00919602b82d48635 | |
| parent | 55a29ccad28fe8bd4ab53d25ed7a96345aa2f94b (diff) | |
Reword library conflict paragraph.
| -rw-r--r-- | chapter08/pkgmgt.xml | 24 |
1 files 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.</para> </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> <listitem> <para>If a package containing a shared library is updated, |