Changeset 24ca7aa for introduction/important/pkgmgt.xml
- Timestamp:
- 05/30/2005 09:44:19 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- a71ee9cb
- Parents:
- cec675bd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/pkgmgt.xml
rcec675bd r24ca7aa 48 48 <title>Upgrade Issues</title> 49 49 50 <para>A Package Manager makes it easy to upgrade to newer versions when 51 they are released. Generally the instructions in the LFS and BLFS Book can be 52 used to upgrade to the newer versions. Here are some points that you should 50 <para>A Package Manager makes it easy to upgrade to newer versions when 51 they are released. Generally the instructions in the LFS and BLFS Book can be 52 used to upgrade to the newer versions. Here are some points that you should 53 53 be aware of when upgrading packages, especially on a running system.</para> 54 54 … … 78 78 </listitem> 79 79 <listitem> 80 <para>If you are upgrading a running system, be on the lookout for packages 80 <para>If you are upgrading a running system, be on the lookout for packages 81 81 that use <command>cp</command> instead of <command>install</command> 82 82 to install files. The latter command is usually safer if the executable or library … … 134 134 135 135 <para>The installation needs to be faked, so that the package thinks that it is 136 installed in <filename class="directory">/usr</filename> though in reality it is 137 installed in <filename class="directory">/usr/pkg</filename> hierarchy. 138 Installing in this manner is not usually a trivial task. For example, consider 139 that you are installing a package libfoo-1.1. The following instructions may 136 installed in <filename class="directory">/usr</filename> though in reality it is 137 installed in <filename class="directory">/usr/pkg</filename> hierarchy. 138 Installing in this manner is not usually a trivial task. For example, consider 139 that you are installing a package libfoo-1.1. The following instructions may 140 140 not install the package properly:</para> 141 141 142 <screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1 142 <screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1 143 143 make 144 144 make install</userinput></screen> … … 211 211 <title>User Based Management</title> 212 212 213 <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann, 214 and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints 215 Project</ulink>. In this scheme, each package is installed as a separate user 216 into the standard locations. Files belonging to a package are easily identified 217 by checking the user id. The features and shortcomings of this approach are 213 <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann, 214 and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints 215 Project</ulink>. In this scheme, each package is installed as a separate user 216 into the standard locations. Files belonging to a package are easily identified 217 by checking the user id. The features and shortcomings of this approach are 218 218 too complex to describe in this section. For the details please see the hint at <ulink 219 219 url="http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt"/>.</para>
Note:
See TracChangeset
for help on using the changeset viewer.