Changeset 1f629e3


Ignore:
Timestamp:
02/16/2004 01:29:19 AM (20 years ago)
Author:
Tushar Teredesai <tushar@…>
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, gimp3, 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:
46000ef
Parents:
2532d2e
Message:

Minor fixes to pkg mgt section

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • introduction/important/pkgmgt.xml

    r2532d2e r1f629e3  
    2020the goals of these books - Teaching how a Linux System is built.</para></listitem>
    2121<listitem><para>There are multiple solutions for package management, each having
    22 its strengths and drawbacks.</para></listitem>
     22its strengths and drawbacks. Including one that satifies all audiences is
     23difficult.</para></listitem>
    2324</itemizedlist>
    2425
     
    3132<title>Upgrade Issues</title>
    3233
    33 <para>Following are some points that you should be aware of when upgrading
     34<para>A Package Manager makes it easy to upgrade to newer versions as and when they
     35are released. Generally the instructions in the <acronym>LFS</acronym> and
     36<acronym>BLFS</acronym> Book can be used to upgrade to the newer versions.
     37Following are some points that you should be aware of when upgrading
    3438packages, especially on a running system.</para>
    3539
     
    6670<title>Package Management Techniques</title>
    6771
    68 <para>The following are some common package management techniques.</para>
     72<para>The following are some common package management techniques. Before
     73making a decision on a package manager, do a research on the various
     74techniques, particularly the drawbacks of the particular scheme.</para>
    6975
    7076<sect3>
     
    8086
    8187<sect3>
    82 <title>Install in seperate directories</title>
     88<title>Install in separate directories</title>
    8389
    8490<para>This is a simplistic package management that does not need any extra package
    85 to manage the installations. Each package is installed in a seperate directory.
     91to manage the installations. Each package is installed in a separate directory.
    8692For example, package foo-1.1 is installed in <filename>/usr/pkg/foo-1.1</filename>
    8793and a symlink is made from <filename>/usr/pkg/foo</filename> to
     
    160166calls that modify the filesystem. For this approach to work, all the executables
    161167need to be dymanically linked without the suid or sgid bit. Preloading the
    162 library may cause some unwanted side-effects during installation.</para>
     168library may cause some unwanted side-effects during installation; hence
     169do perform some tests to ensure that the package manager does not break
     170anything and logs all the appropriate files.</para>
    163171
    164172</sect3>
     
    167175<title>Creating Package Archives</title>
    168176
    169 <para>In this scheme, the package installation is faked into a seperate
     177<para>In this scheme, the package installation is faked into a separate
    170178tree as described in the Symlink style package management. After the
    171179installation, a package archive is created using the installed files.
     
    185193devised by Matthias Benkmann, and is available from the <ulink
    186194url="http://www.linuxfromscratch.org/hints/">Hints Project</ulink>.
    187 In this scheme, each package is installed as a seperate user into
     195In this scheme, each package is installed as a separate user into
    188196the standard locations. Files belonging to a package are easily
    189197identified by checking the user id. The features and shortcomings
Note: See TracChangeset for help on using the changeset viewer.