Ignore:
Timestamp:
05/29/2004 08:25:12 AM (20 years ago)
Author:
Igor Živković <igor@…>
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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
3b7081ba
Parents:
bb0d842b
Message:

applied Randy's grammar and spelling fixes

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2232 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/pkgmgt.xml

    rbb0d842b raa15d3e  
    9999mentioned in <xref linkend="intro-important-beyond"/> need to be expanded to
    100100include <filename>/usr/pkg/foo</filename>. For more than a few packages,
    101 this scheme becomes unmanagable.</para>
     101this scheme becomes unmanageable.</para>
    102102
    103103</sect3>
     
    111111to expand the environment variables. Though the symlinks can be created by the user,
    112112to automate the creation, many package managers have been written on this approach.
    113 Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
     113A few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
    114114
    115115<para>The installation needs to be faked, so that the package thinks that it is
    116 installed in <filename>/usr</filename> though in reality it is installed in
    117 <filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
     116installed in <filename class="directory">/usr</filename> though in reality it is installed in
     117<filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
    118118task. For example, consider that you are installing a package libfoo-1.1. The following
    119119instructions may not install the package properly:</para>
Note: See TracChangeset for help on using the changeset viewer.