linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-02-03 23:07:23 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Minor fixes to pkg mgt section

Browse Source 
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1816 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Tushar Teredesai 2004-02-16 01:29:19 +00:00
parent 2532d2e8fc
commit 1f629e3014
1 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
introduction/important/pkgmgt.xml
View File

@ -19,7 +19,8 @@ or <acronym>BLFS</acronym>:</para>
<listitem><para>Dealing with package management takes the focus away from
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>
<para>There are some hints written on the topic of package management. Visit
@ -30,7 +31,10 @@ to find if one of them fits your need.</para>
<sect2>
<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>
<itemizedlist>
@ -65,7 +69,9 @@ is already loaded in memory.</para></listitem>
<sect2>
<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>
<title>It is all in my head!</title>
@ -79,10 +85,10 @@ when a package is changed.</para>
</sect3>
<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
<filename>/usr/pkg/foo-1.1</filename>. When installing a new version foo-1.2,
@ -159,14 +165,16 @@ attaching itself to various executables such as <command>cp</command>,
<command>install</command>, <command>mv</command> and tracking the system
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>
<sect3>
<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.
This archive is then used to install the package either on the local
@ -184,7 +192,7 @@ approach are RPM, pkg-utils, Debian's apt, Gentoo's Portage system.</para>
<para>This scheme, that is unique to <acronym>LFS</acronym>, was
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
of this approach are too complex to describe in this section. For