Penguin
Recent Changes
Blame: dpkg-scanpackages(8)
EditPageHistoryDiffInfoLikePages
Annotated edit history of dpkg-scanpackages(8) version 2, including all changes. View license author blame.
Rev Author # Line
1 perry 1 !!NAME
2
3 dpkg-scanpackages - create Packages files
2 CraigBox 4
1 perry 5 !!SYNOPSIS
6
2 CraigBox 7 __dpkg-scanpackages__ ''binarydir overridefile'' [[''pathprefix''] ____ ''Packages''
1 perry 8
9 !!DESCRIPTION
10
2 CraigBox 11 __dpkg-scanpackages__ sorts through a tree of Debian binary packages and creates a Packages file, used by dselect(8) to tell the user what packages are available for installation. These Packages files are the same as those found on Debian archive sites and CD-ROMs. You might use __dpkg-scanpackages__ yourself if making a directory of local packages to install on a cluster of machines.
1 perry 12
2 CraigBox 13 ''binarydir'' is the name of the binary tree to process (for example, __contrib/binary-i386__). It is best to
14 make this relative to the root of the Debian archive, because every Filename field in the new Packages file will start with this string.
1 perry 15
2 CraigBox 16 ''overridefile'' is the name of a file to read which contains information about how the package fits into the distribution; see below.
1 perry 17
2 CraigBox 18 ''pathprefix'' is an optional string to be prepended to the Filename fields.
1 perry 19
20 !!THE OVERRIDE FILE
21
2 CraigBox 22 While most information about a package can be found in the control file, some must be filled in by the distribution
23 czars rather than by the maintainer, because they relate to the arrangement of files for release rather than the actual
24 dependencies and description of the package. This information is found in the override file.
1 perry 25
2 CraigBox 26 The override file has a simple whitespace-delimited format. Comments are allowed (denoted with a __#__).
1 perry 27
2 CraigBox 28 ''package priority section'' [[''maintainerinfo'']
1 perry 29
2 CraigBox 30 ''package'' is the name of the package. Entries in the override file for packages not found in the binary tree are
1 perry 31 ignored.
32
2 CraigBox 33 ''priority'' and ''section'' place the package within the release tree; these ought not to be found in the control
34 file. If the package is found in a subdirectory of ''binarydir'', that will be checked against ''section''.
1 perry 35
2 CraigBox 36 ''maintainerinfo'', if present, can be either the name of a maintainer for an unconditional override, or else
37 ''oldmaintainer'' __=__ ''newmaintainer'' to perform a substitution.
1 perry 38
2 CraigBox 39 The override files used to make the official Packages lists may be found in the ''indices'' directory on any Debian
40 mirror.
1 perry 41
42 !!DIAGNOSTICS
43
2 CraigBox 44 __dpkg-scanpackages__ outputs the usual self-explanatory errors. It also warns about packages that are in the wrong subdirectory, are duplicated, have a Filename field in their control file, are missing from the override file, or have
45 maintainer substitutions which do not take effect.
1 perry 46
47 !!SEE ALSO
48
49 dpkg(8), dselect(8).
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.

PHP Warning

lib/blame.php:177: Warning: Invalid argument supplied for foreach() (...repeated 8 times)