Changeset 3f3931b0 for chapter06/pkgmgt.xml

Timestamp:

02/07/2006 07:39:29 PM (18 years ago)

Author:

Manuel Canales Esparcia <manuel@…>

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.3, 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:

ddd5542

Parents:

1ca11cd

Message:

Indenting chapter 6, part 9

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

File:

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

chapter06/pkgmgt.xml

@@ -1 +1 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
@@ -7 +7 @@
 
 <sect1 id="ch-system-pkgmgt">
+  <?dbhtml filename="pkgmgt.html"?>
+
   <title>Package Management</title>
-  <?dbhtml filename="pkgmgt.html"?>
 
   <para>Package Management is an often requested addition to the LFS Book. A
@@ -19 +20 @@
   issues that may arise when upgrading packages.</para>
 
-  <para>Some reasons why no package manager is mentioned in LFS or BLFS include:  </para>
+  <para>Some reasons why no package manager is mentioned in LFS or BLFS
+  include:</para>
 
   <itemizedlist>
@@ -38 +40 @@
   fits your need.</para>
 
-  <note><para>As no particular package management technique is mentioned in LFS,
-  the commands in the remainder of this book must be performed while logged in
-  as user <emphasis>root</emphasis> and no longer as user
-  <emphasis>lfs</emphasis>. Also, double check that <envar>$LFS</envar> is set.
-  </para></note>
+  <note>
+    <para>As no particular package management technique is mentioned in LFS,
+    the commands in the remainder of this book must be performed while logged in
+    as user <systemitem class="username">root</systemitem> and no longer as user
+    <systemitem class="username">lfs</systemitem>. Also, double check that
+    <envar>$LFS</envar> is set.</para>
+  </note>
 
   <sect2>
@@ -54 +58 @@
     <itemizedlist>
       <listitem>
-        <para>If one of the toolchain packages
-        (<application>Glibc</application>, <application>GCC</application> or
-        <application>Binutils</application>) needs to be upgraded to a newer
-        minor version, it is safer to rebuild LFS. Though you
-        <emphasis>may</emphasis> be able to get by rebuilding all the packages
-        in their dependency order, we do not recommend it. 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.4 to
-        glibc-2.3.5 will not usually cause any problems.</para>
+        <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs
+        to be upgraded to a newer minor version, it is safer to rebuild LFS.
+        Though you <emphasis>may</emphasis> be able to get by rebuilding all
+        the packages in their dependency order, we do not recommend it. 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.4
+        to glibc-2.3.5 will not usually cause any problems.</para>
       </listitem>
 
@@ -110 +112 @@
       need any package management because they plan on rebuilding the entire
       system when a package is changed.</para>
+
     </sect3>
 
@@ -130 +133 @@
       include <filename>/usr/pkg/foo</filename>. For more than a few packages,
       this scheme becomes unmanageable.</para>
+
     </sect3>
 
@@ -169 +173 @@
 make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
 
-      <para>Most packages support this approach, but there are some which do
-      not. For the non-compliant packages, you may either need to manually
-      install the package, or you may find that it is easier to install some
-      problematic packages into <filename class='directory'>/opt</filename>.
-      </para>
+      <para>Most packages support this approach, but there are some which do not.
+      For the non-compliant packages, you may either need to manually install the
+      package, or you may find that it is easier to install some problematic
+      packages into <filename class='directory'>/opt</filename>.</para>
+
     </sect3>
 
@@ -191 +195 @@
       is installed at a time. The logs are not reliable if two packages are
       being installed on two different consoles.</para>
+
     </sect3>
 
@@ -206 +211 @@
       ensure that the package manager does not break anything and logs all the
       appropriate files.</para>
+
     </sect3>
 
@@ -215 +221 @@
       installation, a package archive is created using the installed files.
       This archive is then used to install the package either on the local
-      machine or can even be used to install the package on other machines.
-      </para>
+      machine or can even be used to install the package on other machines.</para>
 
       <para>This approach is used by most of the package managers found in the
@@ -226 +231 @@
       package management for LFS systems is located at <ulink
       url="&hints-root;/fakeroot.txt"/>.</para>
+
     </sect3>
 
@@ -237 +243 @@
       checking the user ID. The features and shortcomings of this approach are
       too complex to describe in this section. For the details please see the
-      hint at <ulink
-      url="&hints-root;/more_control_and_pkg_man.txt"/>.</para>
+      hint at <ulink url="&hints-root;/more_control_and_pkg_man.txt"/>.</para>
+
     </sect3>