[SCM] live-manual branch, debian-next, updated. debian/3.0_a14-1-22-g5cf3e2f

[chals]

The following commit has been merged in the debian-next branch:
commit 5cf3e2fd6a0130e8aba1a81996cd1abbb28dd093
Author: chals <chals at altorricon.com>
Date:   Sat Aug 4 23:32:24 2012 +0200

    Copying minimal.chroot hook to config/hooks and thus making the example work.

diff --git a/manual/en/user_examples.ssi b/manual/en/user_examples.ssi
index fa042df..3a45a18 100644
--- a/manual/en/user_examples.ssi
+++ b/manual/en/user_examples.ssi
@@ -223,12 +223,13 @@ Enjoy.
 
 *{Use case:}* Create a standard image with some components removed in order to fit on a 128M USB key with a little space left over to use as you see fit.
 
-When optimizing an image to fit a certain media size, you need to understand the tradeoffs you are making between size and functionality. In this example, we trim only so much as to make room for additional material within a 128M media size, but without doing anything to destroy integrity of the packages contained within, such as the purging of locale data via the /{localepurge}/ package, or other such "intrusive" optimizations. Of particular note, in order to understand what #{--hooks minimal.chroot}# does you should take a look at #{/usr/share/doc/live-build/examples/hooks}#
+When optimizing an image to fit a certain media size, you need to understand the tradeoffs you are making between size and functionality. In this example, we trim only so much as to make room for additional material within a 128M media size, but without doing anything to destroy integrity of the packages contained within, such as the purging of locale data via the /{localepurge}/ package, or other such "intrusive" optimizations. Of particular note, in order to understand what the #{minimal.chroot}# hook does you should take a look at #{/usr/share/doc/live-build/examples/hooks}#
 
 code{
 
- $ lb config -k 486 --hooks minimal.chroot --apt-indices false \
+ $ lb config -k 486 --apt-indices false \
      --memtest none --apt-recommends false --includes none
+ $ cp /usr/share/doc/live-build/examples/hooks/minimal.chroot config/hooks
 
 }code
 
@@ -240,9 +241,9 @@ code{
 
 }code
 
-On the author's system at the time of writing this, the above configuration produced a 101Mbyte image. This compares favourably with the 182Mbyte image produced by the default configuration in {Tutorial 1}#tutorial-1.
+On the author's system at the time of writing this, the above configuration produced a 95Mbyte image. This compares favourably with the 182Mbyte image produced by the default configuration in {Tutorial 1}#tutorial-1.
 
-The biggest space-saver here, compared to building a standard image on an #{i386}# architecture system, is to select only the #{486}# kernel flavour instead of the default #{-k "486 686-pae"}#. Leaving off APT's indices with #{--apt-indices false}# also saves a fair amount of space, the tradeoff being that you need to #{apt-get update}# before using apt in the live system. Activating the #{minimal}# hook removes some unused packages and files. Dropping recommended packages with #{--apt-recommends false}# saves some additional space, at the expense of omitting some packages you might otherwise expect to be there, such as /{firmware-linux-free}/ which may be needed to support certain hardware. The remaining options shave off additional small amounts of space. It's up to you to decide if the functionality that is sacrificed with each optimization is worth the loss in functionality.
+The biggest space-saver here, compared to building a standard image on an #{i386}# architecture system, is to select only the #{486}# kernel flavour instead of the default #{-k "486 686-pae"}#. Leaving off APT's indices with #{--apt-indices false}# also saves a fair amount of space, the tradeoff being that you need to #{apt-get update}# before using apt in the live system. The execution of the #{minimal}# hook removes some unused packages and files. Dropping recommended packages with #{--apt-recommends false}# saves some additional space, at the expense of omitting some packages you might otherwise expect to be there, such as /{firmware-linux-free}/ which may be needed to support certain hardware. The remaining options shave off additional small amounts of space. It's up to you to decide if the functionality that is sacrificed with each optimization is worth the loss in functionality.
 
 2~ A localized KDE desktop and installer
 

-- 
live-manual