This is a brief summary of the procedure for converting a pre-2.0.0.0-format source package into the new format.
You are strongly advised to download and examine the hello
package, and to read the section in the dpkg
programmers' manual
describing the source packaging tools. More detail about the exact
functionality of these tools is available in dpkg-source(1)
.
Local variables: mode: debian-changelog End:
dpkg-gencontrol
's variable substitution features to
achieve the same effect. Use debian/substvars if you need to put
unusally-generated information (apart from details of .deb files)
in the .changes file too.
source
and diff
and any
changes
and dist
targets. These things now happen in
a package-independent way and are not done by debian/rules.
binary
target into binary-arch
and
binary-indep
; in many cases all of binary
should go
into binary-arch
. Create the binary
target and the
unused of the two other binary-*
targets if there is one - you can
copy the ones from the hello
package.
binary
target to use dpkg-gencontrol
to
make the package control file(s). Move it to after all the files have been
installed but just before the last chown
and chmod
in
the target.
dpkg-shlibdeps
to determine its shared
library dependencies and substitute them in. Shared library dependencies
should no longer be hardwired in the source package.
The use of -sa on dpkg-buildpackage
and
dpkg-genchanges
is important when doing the first build/uploading
of a new-format source package. Unless this happens to be Debian revision
0 or 1 by default the original source tarfile will
not be included in the uploaded files listed in the .changes file,
and so it won't be installed on the FTP site. -sa requests that
the original source be included regardless.
ijackson@gnu.ai.mit.edu
bweaver@debian.org
schwarz@debian.org
srivasta@debian.org
debian-policy@lists.debian.org