Ignore:
Timestamp:
May 17, 2006, 1:20:04 PM (17 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
13bd751
Parents:
76246b3
Message:

r3564@server (orig r1629): chris | 2006-05-17 13:05:26 -0700
More text updates, mostly to change LFS references to CLFS

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/final-system/common/pkgmgt.xml

    r76246b3 r9f08378  
    1111  <title>Package Management</title>
    1212
    13   <para>Package Management is an often requested addition to the LFS Book. A
     13  <para>Package Management is an often-requested addition to the CLFS Book. A
    1414  Package Manager allows tracking the installation of files making it easy to
    1515  remove and upgrade packages. Before you begin to wonder, NO&mdash;this section
     
    2020  issues that may arise when upgrading packages.</para>
    2121
    22   <para>Some reasons why no specific package manager is recommended in LFS or
    23   BLFS include:</para>
     22  <para>Some reasons why no specific package manager is recommended in
     23  CLFS or BLFS include:</para>
    2424
    2525  <itemizedlist>
     
    4444
    4545    <para>A Package Manager makes it easy to upgrade to newer versions when they
    46     are released. Generally the instructions in the LFS and BLFS Book can be
     46    are released. Generally the instructions in the CLFS and BLFS Book can be
    4747    used to upgrade to the newer versions. Here are some points that you should
    4848    be aware of when upgrading packages, especially on a running system.</para>
     
    5151      <listitem>
    5252        <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs
    53         to be upgraded to a newer minor version, it is safer to rebuild LFS.
    54         Though, you <emphasis>may</emphasis> be able to get by rebuilding all
    55         the packages in their dependency order, we do not recommend it. For
    56         example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
    57         to rebuild. For micro version updates, a simple reinstallation usually
    58         works, but is not guaranteed. For example, upgrading from glibc-2.3.4
    59         to glibc-2.3.5 will not usually cause any problems.</para>
     53        to be upgraded to a newer minor version, it is safer to
     54        rebuild CLFS. Though you <emphasis>may</emphasis> be able to get by
     55        rebuilding all the packages in their dependency order, we do not
     56        recommend it. For example, if glibc-2.2.x needs to be updated to
     57        glibc-2.3.x, it is safer to rebuild. For micro version updates, a
     58        simple reinstallation usually works, but is not guaranteed. For
     59        example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not
     60        usually cause any problems.</para>
    6061      </listitem>
    6162
     
    229230      <title>User Based Management</title>
    230231
    231       <para>This scheme, unique to LFS, was devised by Matthias Benkmann, and is
     232      <para>This scheme, unique to the LFS project, was devised by Matthias Benkmann, and is
    232233      available from the <ulink url="&hints-root;">Hints Project</ulink>. In
    233234      this scheme, each package is installed as a separate user into the
Note: See TracChangeset for help on using the changeset viewer.