Changeset 2db19cb for chapter08/pkgmgt.xml
- Timestamp:
- 04/27/2021 08:07:54 AM (3 years ago)
- Branches:
- ml-11.0, multilib
- Children:
- 88bdbb7
- Parents:
- feed564d (diff), c461bd9 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/pkgmgt.xml
rfeed564d r2db19cb 72 72 use the new library version. You should not remove the previous 73 73 libraries unless all the dependent packages are recompiled.</para> 74 </listitem> </itemizedlist> 74 </listitem> 75 76 <listitem> <para>If a package containing a shared library is updated, 77 and the name of library doesn't change, but the version number of the 78 library <emphasis role="bold">file</emphasis> decreases (for example, 79 the name of the library is kept named 80 <filename class='libraryfile'>libfoo.so.1</filename>, 81 but the name of library file is changed from 82 <filename class='libraryfile'>libfoo.so.1.25</filename> to 83 <filename class='libraryfile'>libfoo.so.1.24</filename>), 84 you should remove the library file from the previously installed version 85 (<filename class='libraryfile'>libfoo.so.1.25</filename> in the case). 86 Or, a <command>ldconfig</command> run (by yourself using a command 87 line, or by the installation of some package) will reset the symlink 88 <filename class='libraryfile'>libfoo.so.1</filename> to point to 89 the old library file because it seems having a <quote>newer</quote> 90 version, as its version number is larger. This situation may happen if 91 you have to downgrade a package, or the package changes the versioning 92 scheme of library files suddenly.</para> </listitem> 93 94 </itemizedlist> 75 95 76 96 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.