1 .\" Hey, Emacs! This is an -*- nroff -*- source file.
2 .\" Authors: Ian Jackson
3 .TH DPKG\-SOURCE 8 "7th Auguest" "Debian Project" "Debian GNU/Linux manual"
5 dpkg\-source, dpkg\-genchanges, dpkg\-gencontrol,
6 dpkg\-buildpackage, dpkg\-distaddfile, dpkg\-parsechangelog
7 \- Debian source packaging tools
11 .IR directory " [" archive | directory ]
15 .IR archive " [" control\-file\-name " ..]"
19 .IR archive " [" control\-field\-name " ...]"
26 .BR -x | --extract | -X | --vextract
29 .B dpkg-deb --fsys-tarfile
36 packs, unpacks and provides information about Debian archives.
40 to install and remove packages from your system.
46 with whatever options you want to pass to
47 .BR dpkg\-deb ". " dpkg
48 will spot that you wanted
54 Creates a debian archive from the filesystem tree stored in
55 .IR directory ". " directory
58 subdirectory, which contains the control information files such
59 as the control file itself. This directory will
61 appear in the binary package's filesystem archive, but instead
62 the files in it will be put in the binary package's control
66 .BR \-\-no\-check ", " dpkg\-deb "
69 and parse it. It will check it for syntax errors and other problems,
70 and display the name of the binary package being built.
72 will also check the permissions of the maintainer scripts and other
75 control information directory.
81 will write the package into the file
82 .IR directory \fB.deb\fR.
84 If the archive to be created already exists it will be overwritten.
86 If the second argument is a directory then
88 will write to the file
89 .IB package _ version _ arch .deb\fR,
91 .IB package _ version .deb
94 field is present in the package control file. When a target directory
95 is specified, rather than a file, the
97 option may not be used (since
99 needs to read and parse the package control file to determine which
103 Provides information about a binary package archive.
106 .IR control\-file\-name s
107 are specified then it will print a summary of the contents of the
108 package as well as its control file.
111 .IR control\-file\-name s
114 will print them in the order they were specified; if any of the
115 components weren't present it will print an error message to stderr
116 about each one and exit with status 2.
118 .BR \-\-field ", " -f
119 Extracts control file information from a binary package archive.
122 .BR control\-file\-field s
123 are specified then it will print the whole control file.
125 If any are specified then
127 will print their contents, in the order in which they appear in the
128 control file. If more than one
129 .BR control\-file\-field
132 will precede each with its field name (and a colon and space).
134 No errors are reported for fields requested but not found.
136 .BR --contents ", " -c
137 Lists the contents of the filesystem tree archive portion of the
138 package archive. It is currently produced in the format generated by
142 .BR --extract ", " -x ", " \-\-vextract ", " -X
143 Extracts the filesystem tree from a package archive into the specified
146 .BR \-\-vextract " (" -X ")"
147 prints a listing of the files extracted as it goes, while
148 .BR \-\-extract " (" -x ")"
149 is silent unless an error occurs.
151 Note that extracting a package to the root directory will
153 result in a correct installation ! Use
158 (but not its parents) will be created if necessary.
161 Extracts the filesystem tree data from a binary package and sends it
162 to standard output in
164 format. Together with
166 this can be used to extract a particular file from a package archive.
168 .BR --control ", " -e
169 Extracs the control information files from a package archive into the
172 If no directory is specified then a subdirectory
174 in the current directory is used.
176 The target directory (but not its parents) will be created if
182 usage message, giving a summary of its options and their uses.
190 Prints information about
192 copyright licensing and lack of warranty. (The American spelling
200 builds a `new' format archive. This is the default.
205 to build an `old' format archive. This old archive format is less
206 easily parsed by non-Debian tools and is now obsolete; its only use is
207 when building packages to be parsed by versions of dpkg older than
208 0.93.76 (September 1995), which was released as i386 a.out only.
212 .BR "dpkg\-deb \-\-build" 's
213 usual checks on the proposed contents of an archive. You can build
214 any archive you want, no matter how broken, this way.
217 Enables debugging output. This is not very interesting.
222 does the wrong thing.
224 There is no authentication on
226 files; in fact, there isn't even a straightforward checksum.
228 Do not attempt to use just
230 to install software ! You must use
232 proper to ensure that all the files are correctly placed and the
233 package's scripts run and its status and contents recorded.
242 and this manpage were written by Ian Jackson. They are
243 Copyright (C)1995-1996
244 by him and released under the GNU General Public Licence; there is NO
246 .B /usr/doc/copyright/dpkg
248 .B /usr/doc/copyright/GPL