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.
its deps has gone into testing yet, and some deps are not even available on some architectures. Closes: #202965 * Stop #including the deps of packages in Key, since it's pointless and only makes it more fragile. #including in Packages is still ok. * Don't fail to build on missing key packages, since there might not be an apt cache to look at on some buildd's, or it might not include contrib. * The gnome-office metapackage vanished. The desktop task already includes koffice. OOo is still mired in contrib. Took the best of a bad lot and put OOo in as the only office software in the office task. * Commented out mozilla-locale-es as the package is currently broken. * Rene Engelhard - Make all the language tasks pull in OOo and kde langage packages consistently. - Replace toshutils with toshset which does not need X or a kernel interface.
|20 years ago|
|README||20 years ago|
|basic-desktop||20 years ago|
|c-dev||20 years ago|
|chinese-s||20 years ago|
|chinese-t||20 years ago|
|cyrillic||20 years ago|
|danish||20 years ago|
|database-server||20 years ago|
|desktop||20 years ago|
|dialup||20 years ago|
|dns-server||20 years ago|
|file-server||20 years ago|
|french||20 years ago|
|games||20 years ago|
|german||20 years ago|
|japanese||20 years ago|
|java-dev||20 years ago|
|junior||21 years ago|
|kernel-compile||20 years ago|
|korean||20 years ago|
|laptop||20 years ago|
|lsb||20 years ago|
|mail-server||20 years ago|
|news-server||20 years ago|
|office||20 years ago|
|polish||20 years ago|
|print-server||20 years ago|
|python-dev||20 years ago|
|russian||20 years ago|
|science||20 years ago|
|spanish||20 years ago|
|tcltk-dev||20 years ago|
|tex||20 years ago|
|thai||20 years ago|
|unix-server||20 years ago|
|web-server||20 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), Key, and
Packages. The Packages field should include the list of packages one per
line after it, indented by one space each, like so:
When the task is selected, any of those packages that are available will be
The Key field is the same, but packages listed in it must be available or
the task should not be displayed at all. There's no need to list packages
in the Packages field if they are listed as Key.
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 Key however.
List only real packages, not virtual packages.
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.
Debian developers aside from the tasksel maintenance team may take over
maintenance of tasks. Talk with the tasksel developers first, and then put
your name in a Maintainer field in the task file you're maintaining.