Changeset 8d5322e for chapter08/pkgmgt.xml
- Timestamp:
- 11/18/2022 07:41:41 AM (23 months ago)
- Branches:
- multilib, xry111/multilib
- Children:
- 46405a5b
- Parents:
- 16a1647 (diff), 7115c88 (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. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/pkgmgt.xml
r16a1647 r8d5322e 13 13 <para>Package Management is an often requested addition to the LFS Book. A 14 14 Package Manager tracks the installation of files, making it easier to 15 remove and upgrade packages. As well as the binary and library files, a 16 package manager will handle the installation of configuration files. Before 15 remove and upgrade packages. A good package manager will also handle the 16 configuration files specially to keep the user configuration when the 17 package is reinstalled or upgraded. Before 17 18 you begin to wonder, NO—this section will not talk about nor recommend 18 any particular package manager. What it providesis a roundup of the more19 any particular package manager. What it does provide is a roundup of the more 19 20 popular techniques and how they work. The perfect package manager for you may 20 21 be among these techniques, or it may be a combination of two or more of these … … 62 63 63 64 <listitem> 64 <para>If Linux API headers or glibc need to be upgraded to a newer65 version, (e.g., from glibc-2.31 to glibc-2.32), it is safer to65 <para>If the Linux API headers or Glibc need to be upgraded to a newer 66 version, (e.g., from Glibc-2.31 to Glibc-2.32), it is safer to 66 67 rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild 67 68 all the packages in their dependency order, we do not recommend … … 203 204 reality it is installed in the 204 205 <filename class="directory">/usr/pkg</filename> hierarchy. Installing in 205 this manner is not usually a trivial task. For example, consider thatyou206 this manner is not usually a trivial task. For example, suppose you 206 207 are installing a package libfoo-1.1. The following instructions may 207 208 not install the package properly:</para> … … 322 323 another computer with the same architecture as the base system is as 323 324 simple as using <command>tar</command> on the LFS partition that contains 324 the root directory (about 250MB uncompressed for a base LFS build), copying 325 the root directory (about 900MB uncompressed for a basic LFS build), copying 326 <!-- D. Bryant created LFS 11.2 in October 2022; 900MB is (roughly) the size of his rsync archive. --> 325 327 that file via network transfer or CD-ROM / USB stick to the new system, and expanding 326 328 it. After that, a few configuration files will have to be changed.
Note:
See TracChangeset
for help on using the changeset viewer.