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

pkgmgmt: Revert some of reword for "dependency hell" from Bruce

Browse Source 
Use "library name" (instead of "library version") for SONAME (for now).
And "conflicting locations" may not be a problem if the symbol is at two
locations but they are exactly same (or ABI compatible).

For the details see lfs-dev discussion.

The current word is still not perfect (we've not defined "the name of a
shared library" at all), so I guess we'll need to make a major revision
for the entire "upgrading issue with shared libraries" thing in the
future.
This commit is contained in:
Xi Ruoyao 2023-06-04 19:31:59 +08:00
parent d4a32f958f
commit 5e7593e6f0
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter08/pkgmgt.xml
View File

@ -86,12 +86,12 @@
</listitem>
<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
the old and new names 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>), the
package may malfunction because the different revisions of the shared
library present conflicting locations for some symbol names. This can be
library present incompatible definitions 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