You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Joey Hess 23fe9848e0 * Switched from emacs20 to emacs21. Closes: #152018 19 years ago
..
README updates 20 years ago
basic-desktop updates 20 years ago
c-dev updates 20 years ago
chinese-s updates 20 years ago
chinese-t updates 20 years ago
cyrillic updates 20 years ago
danish * Switched from emacs20 to emacs21. Closes: #152018 19 years ago
database-server updates 20 years ago
desktop * Switched from emacs20 to emacs21. Closes: #152018 19 years ago
dialup updates 20 years ago
dns-server updates 20 years ago
file-server updates 20 years ago
fortran-dev updates 20 years ago
french updates 20 years ago
games * Modifications to existing tasks: 21 years ago
german updates 20 years ago
japanese updates 20 years ago
junior updates 20 years ago
korean updates 20 years ago
laptop * Switched from emacs20 to emacs21. Closes: #152018 19 years ago
mail-server updates 20 years ago
news-server updates 20 years ago
office * Switched from emacs20 to emacs21. Closes: #152018 19 years ago
polish updates 20 years ago
print-server updates 20 years ago
python-dev updates 20 years ago
russian updates 20 years ago
science * Modifications to existing tasks: 21 years ago
spanish updates 20 years ago
tcltk-dev updates 20 years ago
tex updates 20 years ago
unix-server * Added Essential: fields to all task files. The idea is to skip display of 20 years ago
web-server updates 20 years ago

README

Files in this directory with lowercase filenames contain descriptions of
verious general tasks a user might want to perform with a Debian system,
lists of packages that they might use to perform the tasks, and grouping
information to make related sets of tasks appear together.

The file format is a rfc-822 style stanza, with fields named Task, Section,
Description (which should include an extended descrition), Essential, and
Packages. The Packages field should include the list of packages one per
line after it, indented by one space each, like so:

Packages:
foo
bar
baz
...

When the task is selected, any of those packages that are available will be
selected.

The Essential field is the same, but packages listed in it must be
available or the task should not be displayed at all. Items listed in the
Essential field must be re-listed in the Packages field, currently, until
the scripts that generate the overrides info are updated to know about this
new field.

Comments may appear in the file, by prefixing a line with a hash mark
('#').

Care should be taken when adding new tasks to ensure that the new task
is suitably generic -- it should be something of value to a large number
(at least 10%) of our users. It must not perform the same general purpose
as some other existing task. It must contain packages that are the ones in
most common use, and software that is of the best perceived quality.

Packages listed for different tasks (and within a single task)
should not conflict, or the results will be rather arbitrary.

Packages that are only available on some architectures, or that may not
be available on the user's installation media may still be listed. This
is no problem, they are simply ignored in those cases. Take care listing
such packages as Essential however.

Users are given the opportunity to drill down and select/unselect
individual packages; the tasks they select only serve as a starting
point. So err on the side of listing too many packages, rather than too
few (but don't go overboard, since many users will not bother with
package-level selection at first).

Keep short descriptions short -- very short -- and to the point. Do not
include details about what individual packages a task includes, tasksel
will do that for you.