diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2023-06-04 19:31:59 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2023-06-04 19:31:59 +0800 |
| commit | 5e7593e6f07b1ca8946e1da8d24952595d365046 (patch) | |
| tree | 7b2cd1b36ab40bf1ad3db46f03b07fb557f69830 | |
| parent | d4a32f958ff99a1e408c156c83d694ac7b5ccd9d (diff) | |
pkgmgmt: Revert some of reword for "dependency hell" from Bruce
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.
| -rw-r--r-- | chapter08/pkgmgt.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index f5e50524b..7104d9cba 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -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 |