gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 14:24:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Reword library conflict paragraph.

Browse Source
This commit is contained in:
Bruce Dubbs 2023-05-27 17:07:58 -05:00
parent 55a29ccad2
commit d0da969c43
1 changed files with 11 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
chapter08/pkgmgt.xml
View File

@ -85,20 +85,18 @@
libraries until all the dependent packages have been recompiled.</para> libraries until all the dependent packages have been recompiled.</para>
</listitem> </listitem>
<listitem><para>If a package is (directly or indirectly) linked to <listitem><para>If a package is (directly or indirectly) linked to both
both the old and new names of one shared library (for example, the the old and new versions of a shared library (for example, the package
package links to both links to both <filename class='libraryfile'>libfoo.so.2</filename> and
<filename class='libraryfile'>libfoo.so.2</filename> and
<filename class='libraryfile'>libbar.so.1</filename>, while the latter <filename class='libraryfile'>libbar.so.1</filename>, while the latter
links to links to <filename class='libraryfile'>libfoo.so.3</filename>), the
<filename class='libraryfile'>libfoo.so.3</filename> in turn), the package may malfunction because the different revisions of the shared
package may malfunction because the different names of the shared library present conflicting locations for some symbol names. This can be
library provide incompatible functions with same symbol names. This caused by recompiling some, but not all, of the packages linked to the
can be caused by recompiling some (but not all) packages linked to the old shared library after the package providing the shared library is
old shared library name after the package providing the shared library upgraded. To avoid the issue, users will need to rebuild every package
is upgraded. To avoid the issue, it's recommended to recompile every linked to a shared library with an updated revision (e.g. libfoo.so.2 to
package linked to a shared library of which the name has been changed libfoo.so.3) as soon as possible.
during an upgrade as soon as possible, in their dependency order.
</para></listitem> </para></listitem>
<listitem> <para>If a package containing a shared library is updated, <listitem> <para>If a package containing a shared library is updated,