diff options
Diffstat (limited to 'chapter08/pkgmgt.xml')
| -rw-r--r-- | chapter08/pkgmgt.xml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index 60c472ad4..7496f09a4 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -12,10 +12,10 @@ <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 handle the + installation of configuration files, and also install the executable files. Before you begin to wonder, NO—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 techniques. This section briefly mentions issues that may arise when upgrading @@ -61,8 +61,8 @@ </listitem> <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 it. </para> @@ -202,7 +202,7 @@ it is installed in <filename class="directory">/usr</filename> though in 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> @@ -321,7 +321,8 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen> depend on the position of files on a disk system. Cloning an LFS build to 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. Configuration files that may need to be updated include: |