cvs commit: BLFS/BOOK/introduction/important pkgmgt.xml

tushar at linuxfromscratch.org tushar at linuxfromscratch.org
Sun Feb 15 17:29:19 PST 2004


tushar      04/02/15 18:29:19

  Modified:    BOOK/introduction/important pkgmgt.xml
  Log:
  Minor fixes to pkg mgt section
  
  Revision  Changes    Path
  1.3       +16 -8     BLFS/BOOK/introduction/important/pkgmgt.xml
  
  Index: pkgmgt.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/pkgmgt.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -u -r1.2 -r1.3
  --- pkgmgt.xml	3 Feb 2004 06:01:09 -0000	1.2
  +++ pkgmgt.xml	16 Feb 2004 01:29:19 -0000	1.3
  @@ -19,7 +19,8 @@
   <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 @@
   <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 @@
   <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 @@
   </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 @@
   <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 @@
   <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
  
  
  



More information about the blfs-book mailing list