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

pkgmgt: Mention the "dependency hell" issue

Browse Source
This commit is contained in:
Xi Ruoyao 2023-05-27 19:05:06 +08:00
parent 0aba9cbb0c
commit 55a29ccad2
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
chapter08/pkgmgt.xml
View File

@ -85,6 +85,22 @@
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
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
<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.
</para></listitem>
<listitem> <para>If a package containing a shared library is updated, <listitem> <para>If a package containing a shared library is updated,
and the name of the library doesn't change, but the version number of the and the name of the library doesn't change, but the version number of the
library <emphasis role="bold">file</emphasis> decreases (for example, library <emphasis role="bold">file</emphasis> decreases (for example,