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

[Ben Armstrong]

The following commit has been merged in the debian-next branch:
commit 0e8271ecf2e3a8c38e41cd02438f6c74e5d7146a
Author: Ben Armstrong <synrg at debian.org>
Date:   Wed Aug 1 17:48:58 2012 -0300

    Explaining multiple lists, dropping includes and tasks, adding generated lists.

diff --git a/manual/en/user_customization-packages.ssi b/manual/en/user_customization-packages.ssi
index 9704220..d289232 100644
--- a/manual/en/user_customization-packages.ssi
+++ b/manual/en/user_customization-packages.ssi
@@ -124,7 +124,7 @@ code{
 
 3~ Local package lists
 
-Whether you list metapackages, individual packages, or a combination of both, all local package lists are stored in #{config/package-lists/}#.
+Whether you list metapackages, individual packages, or a combination of both, all local package lists are stored in #{config/package-lists/}#. Since more than one list can be used, this lends itself well to modular designs. For example, you may decide to devote one list to a particular choice of desktop, another to a collection of related packages that might as easily be used on top of a different desktop. This allows you to experiment with different combinations of sets of packages with a minimum of fuss, sharing common lists between different live image projects.
 
 Package lists that exist in this directory need to have a #{.list}# suffix in order to be processed, and then an additional stage suffix, #{.chroot}# or #{.binary}# to indicate which stage the list is for.
 
@@ -134,16 +134,16 @@ Package lists that exist in this directory need to have a #{.list}# suffix in or
 
 To make a binary stage list, place a file suffixed with #{.list.binary}# in #{config/package-lists/}#. These packages are not installed in the live filesystem, but are included on the live media under #{pool/}#. You would typically use such a list with one of the non-live installer variants. As mentioned above, if you want this list to be the same as your chroot stage list, simply use the #{.list}# suffix by itself.
 
-3~ Extending a provided package list using includes
+3~ Generated package lists
 
-The package lists that are included with live-build make extensive use of includes. Refer to these in the #{/usr/share/live/build/package-lists/}# directory, as they serve as good examples of how to write your own lists.
+It sometimes happens that the best way to compose a list is to generate it with a script. Any line starting with an exclamation point indicates a command to be executed within the chroot when the image is built. For example, one might include the line #{! grep-aptavail -n -sPackage -FPriority standard | sort}# in a package list to produce a sorted list of available packages with #{Priority: standard}#.
 
-For example, to make a list that includes the predefined #{gnome}# list plus /{iceweasel}/, create #{config/package-lists/my.list.chroot}# with the following contents:
+In fact, selecting packages with #{grep-aptavail}# command (from the #{dctrl-tools}# package) is so useful that #{live-build}# provides a #{Packages}# helper script as a convenience. This script takes two arguments: #{field}# and #{pattern}#. Thus, you can create a list with the following contents:
 
 code{
 
- #include <gnome>
- iceweasel
+ $ lb config
+ $ echo '! Packages Priority standard' > config/package-lists/standard.list.chroot
 
 }code
 
@@ -193,19 +193,6 @@ code{
 
 The nesting of conditionals is not supported.
 
-3~ Tasks
-
-The Debian Installer offers the user choices of a number of preselected lists of packages, each one focused on a particular kind of system, or task a system may be used for, such as "Graphical desktop environment", "Mail server" or "Laptop". These lists are called "tasks" and are supported by APT through the "Task:" field. You can specify one or more tasks in live-build by putting them in a list in #{config/task-lists/}#, as in the example below.
-
-code{
-
- $ lb config
- $ echo "mail-server file-server" >> config/task-lists/my.list.chroot
-
-}code
-
-The primary tasks available in the Debian Installer can be listed with #{tasksel --list-tasks}# in the live system. The contents of any task, including the ones not included in this list, may be examined with #{tasksel --task-packages}#.
-
 3~desktop-and-language-tasks Desktop and language tasks
 
 Desktop and language tasks are special cases that need some extra planning and configuration. Live images are different from Debian Installer images in this respect. In the Debian Installer, if the medium was prepared for a particular desktop environment flavour, the corresponding task will be automatically installed. Thus, there are internal #{gnome-desktop}#, #{kde-desktop}#, #{lxde-desktop}# and #{xfce-desktop}# tasks, none of which are offered in #{tasksel}#'s menu. Likewise, there are no menu entries for tasks for languages, but the user's language choice during the install influences the selection of corresponding language tasks.

-- 
live-manual