Changes in chapter08/pkgmgt.xml [11d5dee:de28837]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/pkgmgt.xml
r11d5dee rde28837 70 70 71 71 <listitem> <para>If a package containing a shared library is updated, and 72 if the name of the library changes, then any packages dynamically72 if the name of the library changes, then any the packages dynamically 73 73 linked to the library need to be recompiled in order to link against the 74 74 newer library. (Note that there is no correlation between the package … … 124 124 125 125 <listitem> 126 <para>If a binary or a shared library is overwr itten, the processes126 <para>If a binary or a shared library is overwrote, the processes 127 127 using the code or data in the binary or library may crash. The 128 128 correct way to update a binary or a shared library without causing 129 the process to crash is toremove it first, then install the new129 the process to crash is: remove it first, then install the new 130 130 version into position. The <command>install</command> command 131 131 provided by <application>Coreutils</application> has already 132 132 implemented this and most packages use it to install binaries and 133 libraries. This means thatyou won't be troubled by this issue most of the time.133 libraries. So you won't be troubled by this issue most of the time. 134 134 However, the install process of some packages (notably Mozilla JS 135 in BLFS) just overwrites the file if it exists and causes acrash, so135 in BLFS) just overwrites the file if it exists and causes crash, so 136 136 it's safer to save your work and close unneeded running processes 137 137 before updating a package.</para>
Note:
See TracChangeset
for help on using the changeset viewer.