Changeset 1f629e3

Timestamp:

02/16/2004 01:29:19 AM (19 years ago)

Author:

Tushar Teredesai <tushar@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 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, ken/inkscape-core-mods, krejzi/svn, lazarus, nosym, perl-modules, plabs/python-mods, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/soup3, xry111/test-20220226

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:

• introduction/important/pkgmgt.xml (modified) (7 diffs)

introduction/important/pkgmgt.xml

@@ -20 +20 @@
 the goals of these books - Teaching how a Linux System is built.</para></listitem>
 <listitem><para>There are multiple solutions for package management, each having
-its strengths and drawbacks.</para></listitem>
+its strengths and drawbacks. Including one that satifies all audiences is
+difficult.</para></listitem>
 </itemizedlist>
 
@@ -31 +32 @@
 <title>Upgrade Issues</title>
 
-<para>Following are some points that you should be aware of when upgrading
+<para>A Package Manager makes it easy to upgrade to newer versions as and when they
+are released. Generally the instructions in the <acronym>LFS</acronym> and
+<acronym>BLFS</acronym> Book can be used to upgrade to the newer versions.
+Following are some points that you should be aware of when upgrading
 packages, especially on a running system.</para>
 
@@ -66 +70 @@
 <title>Package Management Techniques</title>
 
-<para>The following are some common package management techniques.</para>
+<para>The following are some common package management techniques. Before
+making a decision on a package manager, do a research on the various
+techniques, particularly the drawbacks of the particular scheme.</para>
 
 <sect3>
@@ -80 +86 @@
 
 <sect3>
-<title>Install in seperate directories</title>
+<title>Install in separate directories</title>
 
 <para>This is a simplistic package management that does not need any extra package
-to manage the installations. Each package is installed in a seperate directory.
+to manage the installations. Each package is installed in a separate directory.
 For example, package foo-1.1 is installed in <filename>/usr/pkg/foo-1.1</filename>
 and a symlink is made from <filename>/usr/pkg/foo</filename> to
@@ -160 +166 @@
 calls that modify the filesystem. For this approach to work, all the executables
 need to be dymanically linked without the suid or sgid bit. Preloading the
-library may cause some unwanted side-effects during installation.</para>
+library may cause some unwanted side-effects during installation; hence
+do perform some tests to ensure that the package manager does not break
+anything and logs all the appropriate files.</para>
 
 </sect3>
@@ -167 +175 @@
 <title>Creating Package Archives</title>
 
-<para>In this scheme, the package installation is faked into a seperate
+<para>In this scheme, the package installation is faked into a separate
 tree as described in the Symlink style package management. After the
 installation, a package archive is created using the installed files.
@@ -185 +193 @@
 devised by Matthias Benkmann, and is available from the <ulink
 url="http://www.linuxfromscratch.org/hints/">Hints Project</ulink>.
-In this scheme, each package is installed as a seperate user into
+In this scheme, each package is installed as a separate user into
 the standard locations. Files belonging to a package are easily
 identified by checking the user id. The features and shortcomings