Changeset b59b371 for chapter08/pkgmgt.xml

Timestamp:

11/19/2022 08:27:13 AM (18 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

2ef64c4

Parents:

4d3f41c (diff), 651f491 (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.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

File:

• chapter08/pkgmgt.xml (modified) (4 diffs)

chapter08/pkgmgt.xml

@@ -13 +13 @@
   <para>Package Management is an often requested addition to the LFS Book. A
   Package Manager tracks the installation of files, making it easier to
-  remove and upgrade packages. As well as the binary and library files, a
-  package manager will handle the installation of configuration files.  Before
+  remove and upgrade packages. A good package manager will also handle the
+  configuration files specially to keep the user configuration when the
+  package is reinstalled or upgraded.  Before
   you begin to wonder, NO&mdash;this section will not talk about nor recommend
-  any particular package manager. What it provides is a roundup of the more
+  any particular package manager. What it does provide is a roundup of the more
   popular techniques and how they work. The perfect package manager for you may
   be among these techniques, or it may be a combination of two or more of these
@@ -62 +63 @@
 
       <listitem>
-        <para>If Linux API headers or glibc need to be upgraded to a newer
-        version, (e.g.,  from glibc-2.31 to glibc-2.32), it is safer to
+        <para>If the Linux API headers or Glibc need to be upgraded to a newer
+        version, (e.g.,  from Glibc-2.31 to Glibc-2.32), it is safer to
         rebuild LFS.  Though you <emphasis>may</emphasis> be able to rebuild
         all the packages in their dependency order, we do not recommend
@@ -203 +204 @@
       reality it is installed in the
       <filename class="directory">/usr/pkg</filename> hierarchy. Installing in
-      this manner is not usually a trivial task. For example, consider that you
+      this manner is not usually a trivial task. For example, suppose you
       are installing a package libfoo-1.1. The following instructions may
       not install the package properly:</para>
@@ -322 +323 @@
     another computer with the same architecture as the base system is as
     simple as using <command>tar</command> on the LFS partition that contains
-    the root directory (about 250MB uncompressed for a base LFS build), copying
+    the root directory (about 900MB uncompressed for a basic LFS build), copying
+    <!-- D. Bryant created LFS 11.2 in October 2022; 900MB is (roughly) the size of his rsync archive. -->
     that file via network transfer or CD-ROM / USB stick to the new system, and expanding
     it.  After that, a few configuration files will have to be changed.