1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
.\" This manpage is copyright (C) 1996 Michael Shields <shields@crosslink.net>.
.\"
.\" This is free software; you may redistribute it and/or modify
.\" it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2,
.\" or (at your option) any later version.
.\"
.\" This is distributed in the hope that it will be useful, but
.\" WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public
.\" License along with dpkg; if not, write to the Free Software
.\" Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
.TH DPKG-SCANPACKAGES 8 "1996-07-08" "Debian Linux"
.SH NAME
dpkg-scanpackages \- create Packages files
.
.SH SYNOPSIS
.B dpkg-scanpackages
.I binarydir
.I overridefile
.RI [ pathprefix ]
.B >
.I Packages
.
.SH DESCRIPTION
.B dpkg-scanpackages
sorts through a tree of Debian binary packages and creates a Packages
file, used by
.BR 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
.B dpkg-scanpackages
yourself if making a directory of local packages to install on a cluster
of machines.
.PP
.I binarydir
is the name of the binary tree to process (for example,
.BR contrib/binary-i386 ).
It is best to make this relative to the root of the Debian archive,
because every Filename field in the new Packages file will start with
this string.
.PP
.I overridefile
is the name of a file to read which contains information about how the
package fits into the distribution; see below.
.PP
.I pathprefix
is an optional string to be prepended to the Filename fields.
.
.SH THE OVERRIDE FILE
While most information about a package can be found in the control file,
some must be filled in by the distribution czars rather than by the
maintainer, because they relate to the arrangement of files for release
rather than the actual dependencies and description of the package.
This information is found in the override file.
.PP
The override file has a simple whitespace-delimited format. Comments are
allowed (denoted with a
.BR # ).
.PP
.in +5
.I package
.I priority
.I section
.RI [ maintainerinfo ]
.in -5
.PP
.I package
is the name of the package. Entries in the override file for packages
not found in the binary tree are ignored.
.PP
.I priority
and
.I section
place the package within the release tree; these ought not to be found
in the control file. If the package is found in a subdirectory of
.IR binarydir ,
that will be checked against
.IR section .
.PP
.IR maintainerinfo ,
if present, can be either the name of a maintainer for an unconditional
override, or else
.I oldmaintainer
.B =>
.I newmaintainer
to perform a substitution.
.PP
The override files used to make the official Packages lists may be found
in the
.I indices
directory on any Debian mirror.
.
.SH DIAGNOSTICS
.B 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
maintainer substitutions which do not take effect.
.
.SH SEE ALSO
.BR dpkg (8),
.BR dselect (8).
|
