Changeset 511570b
- Timestamp:
- 02/03/2004 06:01:09 AM (20 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 3156dc8
- Parents:
- be43bd3
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/pkgmgt.xml
rbe43bd3 r511570b 3 3 <title>Package Management</title> 4 4 5 <para>Package Management has been one of theoften requested addition5 <para>Package Management is an often requested addition 6 6 to the <acronym>LFS</acronym> Book. A Package Manager allows tracking 7 7 the installation of files making it easy to remove and upgrade packages. … … 10 10 a roundup of the more popular techniques and how they work. The perfect 11 11 package manager for you may be among these techniques or may be a combination 12 of two or more of these techniques. This section alsomentions13 i n brief about some upgrade issues.</para>12 of two or more of these techniques. This section briefly mentions 13 issues that may arise when upgrading packages.</para> 14 14 15 15 <para>Some reasons why no package manager is mentioned in <acronym>LFS</acronym> … … 32 32 33 33 <para>Following are some points that you should be aware of when upgrading 34 pac akges, especially on a running system.</para>34 packages, especially on a running system.</para> 35 35 36 36 <itemizedlist> 37 37 <listitem><para>It is recommended that if one of the toolchain package (glibc, gcc, 38 38 binutils) needs to be upgraded to a newer minor vesion, it is safer to rebuild 39 <acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by by39 <acronym>LFS</acronym>. Though you <emphasis>may</emphasis> be able to get by 40 40 rebuilding all the packages in their dependency order. We do not recommend the 41 latter. For example if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer41 latter. For example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer 42 42 to rebuild. For micro version updates, a simple reinstallation usually works, but 43 43 is not guaranteed. For example, upgrading from glibc-2.3.1 to glibc-2.3.2 will not … … 69 69 70 70 <sect3> 71 <title>It s all in my head!</title>71 <title>It is all in my head!</title> 72 72 73 73 <para>Yes, this is a package management technique. Some folks do not find the … … 109 109 <para>The installation needs to be faked, so that the package thinks that it is 110 110 installed in <filename>/usr</filename> though in reality it is installed in 111 <filename>/ust/pkg</filename> hiera chy. Installing in this manner is not usually a trivial111 <filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial 112 112 task. For example, consider that you are installing a package libfoo-1.1. The following 113 113 instructions may not install the package properly:</para> … … 154 154 <title>LD_PRELOAD based</title> 155 155 156 <para>In this approach, a library is preloaded before installation and during156 <para>In this approach, a library is preloaded before installation. During 157 157 installation, this library tracks the packages that are being installed by 158 158 attaching itself to various executables such as <command>cp</command>,
Note:
See TracChangeset
for help on using the changeset viewer.