| 1 |
This README explains how packages are added to full CDs and DVDs based |
| 2 |
on tasks defined in tasksel. |
| 3 |
|
| 4 |
Note that this document describes the default configuration for debian-cd. |
| 5 |
|
| 6 |
Overview |
| 7 |
======== |
| 8 |
One of the main factors deciding in what order packages are added, |
| 9 |
especially for the first DVD and earlier CDs, is the definition of which |
| 10 |
tasksel tasks should be used. |
| 11 |
|
| 12 |
The list of packages to be added is generated dynamically at build time. |
| 13 |
The procedure is somewhat complex and involves a number of (intermediate) |
| 14 |
files. |
| 15 |
|
| 16 |
The general sequence in which packages are added for "complete" images is: |
| 17 |
1) Packages required by Debian Installer |
| 18 |
2) Packages required to install the base system (debootstrap) |
| 19 |
3) Any packages with priority "standard" or higher |
| 20 |
4) Packages from tasksel tasks |
| 21 |
a) Packages defined as "key" packages for primary tasksel tasks |
| 22 |
b) Packages defined as "key" packages for language tasks (in the order: |
| 23 |
'<language>', '<language>-desktop', '<language>-<desktop>-desktop'); |
| 24 |
only language desktop tasks that correspond to a primary task are |
| 25 |
included |
| 26 |
c) Regular packages from primary tasksel tasks |
| 27 |
d) Regular packages from language tasks |
| 28 |
e) Key packages from secondary tasksel tasks |
| 29 |
f) Key packages from language tasks corresponding to secondary tasksel |
| 30 |
tasks |
| 31 |
g) Regular packages from secondary tasksel tasks |
| 32 |
h) Regular packages from language tasks corresponding to secondary |
| 33 |
tasksel tasks |
| 34 |
5) Other packages in the order of their popularity (popcon score) |
| 35 |
|
| 36 |
A tasksel task is defined as "secondary" by adding a '-' after its name |
| 37 |
in a task.list file; other tasksel tasks are "primary". |
| 38 |
|
| 39 |
Language tasks are added grouped per type, not per language. So with three |
| 40 |
languages (A, B, C) and 'desktop' and 'gnome-desktop' as tasks you'll get: |
| 41 |
A |
| 42 |
B |
| 43 |
C |
| 44 |
A-desktop |
| 45 |
B-desktop |
| 46 |
C-desktop |
| 47 |
A-gnome-desktop |
| 48 |
B-gnome-desktop |
| 49 |
C-gnome-desktop |
| 50 |
|
| 51 |
Note that <language>-desktop tasks are always sorted before any |
| 52 |
<language>-<desktop>-desktop tasks. |
| 53 |
|
| 54 |
Files involved |
| 55 |
============== |
| 56 |
Static task files (can be found in tasks/codename): |
| 57 |
- Debian-generic or Debian-<desktop>: |
| 58 |
top level task file; defines order of other task files to be used, |
| 59 |
including task-essential-[generic|<desktop>] and |
| 60 |
task-full-[generic|<desktop>] |
| 61 |
- task.list.generic or task.list.<desktop>: |
| 62 |
tasksel tasks to be included |
| 63 |
|
| 64 |
Dynamically generated task files created at build time (can be found in |
| 65 |
the subdirectory tasks under the working directory for the build): |
| 66 |
- task.languages |
| 67 |
copy of the actual language list to be used to add language tasks |
| 68 |
(see "Language list used at build time" below) |
| 69 |
- task.gen.[generic|<desktop>].primary: |
| 70 |
contains primary tasks from task.list.[generic|<desktop>] followed by |
| 71 |
corresponding language tasks |
| 72 |
- task.gen.[generic|<desktop>].secondary: |
| 73 |
contains secondary tasks from task.list.[generic|<desktop>] and |
| 74 |
corresponding language tasks |
| 75 |
- task-essential-[generic|<desktop>]: |
| 76 |
list of key packages based on task.gen.[generic|<desktop>].primary; |
| 77 |
corresponds to 3a/3b from overview above |
| 78 |
- task-full-[generic|<desktop>]: |
| 79 |
list of packages based on both task.gen.[generic|<desktop>].primary and |
| 80 |
task.gen.[generic|<desktop>].secondary; corresponds to 3c-3h from overview |
| 81 |
above |
| 82 |
|
| 83 |
The generation of these files is done early in a build by the script |
| 84 |
tools/update_tasks. |