Changeset d327d74 for chapter06/pkgmgt.xml

Timestamp:

01/19/2008 03:25:26 PM (16 years ago)

Author:

Matthew Burgess <matthew@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

9692a57

Parents:

9750afc

Message:

Add a few more details to the package management section, and correct the URL for the LSB specs. Fixes #2073 and #2130.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8452 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

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

chapter06/pkgmgt.xml

@@ -13 +13 @@
   <para>Package Management is an often requested addition to the LFS Book. A
   Package Manager allows tracking the installation of files making it easy to
-  remove and upgrade packages. 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 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 briefly mentions
-  issues that may arise when upgrading packages.</para>
+  remove and upgrade packages. As well as the binary and library files, a
+  package manager will handle the installation of configuration files.  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
+  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 briefly mentions issues that may arise when upgrading
+  packages.</para>
 
   <para>Some reasons why no package manager is mentioned in LFS or BLFS
@@ -183 +185 @@
 
     <sect3>
-      <title>LD_PRELOAD Based</title>
-
-      <para>In this approach, a library is preloaded before installation. During
+      <title>Tracing Installation Scripts</title>
+
+      <para>In this approach, the commands that the installation scripts perform
+      are recorded.  There are two techniques that one can use:</para>
+
+      <para>The <envar>LD_PRELOAD</envar> environment variable can be set to
+      point to a library to be 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>,
@@ -196 +202 @@
       appropriate files.</para>
 
+      <para>The second technique is to use <command>strace</command>, which
+      logs all system calls made during the execution of the installation
+      scripts.</para>
     </sect3>
 
@@ -210 +219 @@
       commercial distributions. Examples of package managers that follow this
       approach are RPM (which, incidentally, is required by the <ulink
-      url="http://lsbbook.gforge.freestandards.org/package.html#RPM">Linux
+      url="http://www.linux-foundation.org/en/Specifications">Linux
       Standard Base Specification</ulink>), pkg-utils, Debian's apt, and
       Gentoo's Portage system.  A hint describing how to adopt this style of