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.
Closes: #116609, #129999 * Make the basic-desktop task incude all of x-window-system (so it gets a WM and xterm and so on), while the desktop task uses just x-window-system-core (because it already has a WM and so on from gnome and kde). Closes: #129217 * Removed pydb from python task, because Colin Watson said to. Closes: #129520 * it.po translation added, da.po added (Closes: #122668), ja.po updated.
|21 years ago|
|README||22 years ago|
|basic-desktop||21 years ago|
|c-dev||22 years ago|
|chinese-s||22 years ago|
|chinese-t||22 years ago|
|cyrillic||22 years ago|
|database-server||22 years ago|
|desktop||21 years ago|
|dialup||22 years ago|
|dns-server||22 years ago|
|file-server||22 years ago|
|fortran-dev||22 years ago|
|french||22 years ago|
|games||22 years ago|
|german||22 years ago|
|japanese||22 years ago|
|junior||22 years ago|
|korean||22 years ago|
|laptop||22 years ago|
|mail-server||22 years ago|
|news-server||22 years ago|
|polish||22 years ago|
|print-server||22 years ago|
|python-dev||21 years ago|
|russian||22 years ago|
|science||22 years ago|
|spanish||22 years ago|
|tcltk-dev||22 years ago|
|tex||22 years ago|
|unix-server||22 years ago|
|web-server||22 years ago|
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), and Packages.
The Packages field should include the list of packages one per line after
it, indented by one space each, like so:
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.
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.