diff options
Diffstat (limited to 'chapter08/pkgmgt.xml')
| -rw-r--r-- | chapter08/pkgmgt.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index 43b9c57d3..c5fcaa4be 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -69,7 +69,7 @@ </listitem> <listitem> <para>If a package containing a shared library is updated, and - if the name of the library changes, then any the packages dynamically + if the name of the library changes, then any packages dynamically linked to the library need to be recompiled in order to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package @@ -123,16 +123,16 @@ </para></listitem> <listitem> - <para>If a binary or a shared library is overwrote, the processes + <para>If a binary or a shared library is overwritten, the processes using the code or data in the binary or library may crash. The correct way to update a binary or a shared library without causing - the process to crash is: remove it first, then install the new + the process to crash is to remove it first, then install the new version into position. The <command>install</command> command provided by <application>Coreutils</application> has already implemented this and most packages use it to install binaries and - libraries. So you won't be troubled by this issue most of the time. + libraries. This means that you won't be troubled by this issue most of the time. However, the install process of some packages (notably Mozilla JS - in BLFS) just overwrites the file if it exists and causes crash, so + in BLFS) just overwrites the file if it exists and causes a crash, so it's safer to save your work and close unneeded running processes before updating a package.</para> </listitem> |