Changeset 511570b

Timestamp:

02/03/2004 06:01:09 AM (20 years ago)

Author:

Tushar Teredesai <tushar@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

3156dc8

Parents:

be43bd3

Message:

Pkg mgt typos

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1767 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/pkgmgt.xml (modified) (6 diffs)

introduction/important/pkgmgt.xml

@@ -3 +3 @@
 <title>Package Management</title>
 
-<para>Package Management has been one of the often requested addition
+<para>Package Management is an often requested addition
 to the <acronym>LFS</acronym> Book. A Package Manager allows tracking
 the installation of files making it easy to remove and upgrade packages.
@@ -10 +10 @@
 a roundup of the more popular techniques and how they work. The perfect
 package manager for you may be among these techniques or may be a combination
-of two or more of these techniques. This section also mentions
-in brief about some upgrade issues.</para>
+of two or more of these techniques. This section briefly mentions
+issues that may arise when upgrading packages.</para>
 
 <para>Some reasons why no package manager is mentioned in <acronym>LFS</acronym>
@@ -32 +32 @@
 
 <para>Following are some points that you should be aware of when upgrading
-pacakges, especially on a running system.</para>
+packages, especially on a running system.</para>
 
 <itemizedlist>
 <listitem><para>It is recommended that if one of the toolchain package (glibc, gcc,
 binutils) needs to be upgraded to a newer minor vesion, it is safer to rebuild
-<acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by by
+<acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by
 rebuilding all the packages in their dependency order. We do not recommend the
-latter. For example if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
+latter. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
 to rebuild. For micro version updates, a simple reinstallation usually works, but
 is not guaranteed. For example, upgrading from glibc-2.3.1 to glibc-2.3.2 will not
@@ -69 +69 @@
 
 <sect3>
-<title>Its all in my head!</title>
+<title>It is all in my head!</title>
 
 <para>Yes, this is a package management technique. Some folks do not find the
@@ -109 +109 @@
 <para>The installation needs to be faked, so that the package thinks that it is
 installed in <filename>/usr</filename> though in reality it is installed in
-<filename>/ust/pkg</filename> hierachy. Installing in this manner is not usually a trivial
+<filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
 task. For example, consider that you are installing a package libfoo-1.1. The following
 instructions may not install the package properly:</para>
@@ -154 +154 @@
 <title>LD_PRELOAD based</title>
 
-<para>In this approach, a library is preloaded before installation and during
+<para>In this approach, a library is preloaded before installation. During
 installation, this library tracks the packages that are being installed by
 attaching itself to various executables such as <command>cp</command>,