Changeset 4afc2603 for introduction/important/pkgmgt.xml
- Timestamp:
- 12/29/2005 01:24:51 AM (18 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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:
- 5254d12
- Parents:
- 17be8c3
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/pkgmgt.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-pkgmgt">8 <sect1 id="pkgmgt"> 9 9 <?dbhtml filename="pkgmgt.html"?> 10 10 … … 43 43 <para>There are some hints written on the topic of package management. Visit 44 44 the <ulink url="&hints-root;">Hints subproject</ulink> 45 to findif one of them fits your need.</para>45 and see if one of them fits your need.</para> 46 46 47 47 <sect2> … … 86 86 <para>If you are upgrading a running system, be on the lookout for packages 87 87 that use <command>cp</command> instead of <command>install</command> 88 to install files. The latter command is usually safer if the executable or library89 is already loaded in memory.</para>88 to install files. The latter command is usually safer if the executable 89 or library is already loaded in memory.</para> 90 90 </listitem> 91 91 </itemizedlist> … … 114 114 <title>Install in Separate Directories</title> 115 115 116 <para>This is a simplistic package management that does not need any extra package117 to manage the installations. Each package is installed in a separate directory.118 For example, package foo-1.1 is installed in116 <para>This is a simplistic package management that does not need any 117 extra package to manage the installations. Each package is installed in a 118 separate directory. For example, package foo-1.1 is installed in 119 119 <filename class='directory'>/usr/pkg/foo-1.1</filename> 120 120 and a symlink is made from <filename>/usr/pkg/foo</filename> to … … 125 125 126 126 <para>The environment variables such as those mentioned in 127 < xref linkend="intro-important-beyond"/> need to be expanded to127 <quote><xref linkend="beyond"/></quote> need to be expanded to 128 128 include <filename>/usr/pkg/foo</filename>. For more than a few packages, 129 129 this scheme becomes unmanageable.</para>
Note:
See TracChangeset
for help on using the changeset viewer.