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

[Ben Armstrong]

The following commit has been merged in the debian-next branch:
commit f56a451a19a8fa2155490b74b0c03194f31ed93a
Author: Ben Armstrong <synrg at debian.org>
Date:   Wed Aug 8 08:29:20 2012 -0300

    Clarifying example uses bash commands.

diff --git a/manual/en/user_installation.ssi b/manual/en/user_installation.ssi
index 5d57e02..c4aa502 100644
--- a/manual/en/user_installation.ssi
+++ b/manual/en/user_installation.ssi
@@ -136,7 +136,7 @@ code{
 
 _* Use applicable generated .deb files
 
-As live-boot and live-config are installed by live-build system, installing the packages in the host system is not sufficient: you should treat the generated .deb files like any other custom packages. Since your purpose for building from source is like to test new things over the short term before the official release, follow {Installing modified or third-party packages}#installing-modified-or-third-party-packages to temporarily include the relevant files in your configuration. In particular, notice that both packages are divided into a generic part, a documentation part and one or more back-ends. Include the generic part, only one back-end matching your configuration, and optionally the documentation. Assuming you are building a live image in the current directory and have generated all .deb files for a single version of both packages in the directory above, this would copy all of the relevant packages including default back-ends:
+As live-boot and live-config are installed by live-build system, installing the packages in the host system is not sufficient: you should treat the generated .deb files like any other custom packages. Since your purpose for building from source is like to test new things over the short term before the official release, follow {Installing modified or third-party packages}#installing-modified-or-third-party-packages to temporarily include the relevant files in your configuration. In particular, notice that both packages are divided into a generic part, a documentation part and one or more back-ends. Include the generic part, only one back-end matching your configuration, and optionally the documentation. Assuming you are building a live image in the current directory and have generated all .deb files for a single version of both packages in the directory above, these bash commands would copy all of the relevant packages including default back-ends:
 
 code{
 

-- 
live-manual