- Timestamp:
- 01/19/2008 03:25:26 PM (17 years ago)
- 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, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 9692a57
- Parents:
- 9750afc
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/pkgmgt.xml
r9750afc rd327d74 13 13 <para>Package Management is an often requested addition to the LFS Book. A 14 14 Package Manager allows tracking the installation of files making it easy to 15 remove and upgrade packages. Before you begin to wonder, NO—this section 16 will not talk about nor recommend any particular package manager. What it 17 provides is a roundup of the more popular techniques and how they work. The 18 perfect package manager for you may be among these techniques or may be a 19 combination of two or more of these techniques. This section briefly mentions 20 issues that may arise when upgrading packages.</para> 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 17 you begin to wonder, NO—this section will not talk about nor recommend 18 any particular package manager. What it provides is a roundup of the more 19 popular techniques and how they work. The perfect package manager for you may 20 be among these techniques or may be a combination of two or more of these 21 techniques. This section briefly mentions issues that may arise when upgrading 22 packages.</para> 21 23 22 24 <para>Some reasons why no package manager is mentioned in LFS or BLFS … … 183 185 184 186 <sect3> 185 <title>LD_PRELOAD Based</title> 186 187 <para>In this approach, a library is preloaded before installation. During 187 <title>Tracing Installation Scripts</title> 188 189 <para>In this approach, the commands that the installation scripts perform 190 are recorded. There are two techniques that one can use:</para> 191 192 <para>The <envar>LD_PRELOAD</envar> environment variable can be set to 193 point to a library to be preloaded before installation. During 188 194 installation, this library tracks the packages that are being installed by 189 195 attaching itself to various executables such as <command>cp</command>, … … 196 202 appropriate files.</para> 197 203 204 <para>The second technique is to use <command>strace</command>, which 205 logs all system calls made during the execution of the installation 206 scripts.</para> 198 207 </sect3> 199 208 … … 210 219 commercial distributions. Examples of package managers that follow this 211 220 approach are RPM (which, incidentally, is required by the <ulink 212 url="http:// lsbbook.gforge.freestandards.org/package.html#RPM">Linux221 url="http://www.linux-foundation.org/en/Specifications">Linux 213 222 Standard Base Specification</ulink>), pkg-utils, Debian's apt, and 214 223 Gentoo's Portage system. A hint describing how to adopt this style of
Note:
See TracChangeset
for help on using the changeset viewer.