Chapter C. Source packages (from old Packaging Manual)

112

dpkg source  b

package

version

This will create the

.dsc

,

.tar.gz

and

.diff.gz

(if appropriate) in the current directory.

dpkg source

does not clean the source tree first   this must be done separately if it is required.

See also `Source packages as archives' on page

117

.

C.1.2

dpkg buildpackage

  overall package building control script

dpkg buildpackage

is a script which invokes

dpkg source

, the

debian/rules

targets

clean

,

build

and

binary

,

dpkg genchanges

and

gpg

(or

pgp

) to build a signed source

and binary package upload.

It is usually invoked by hand from the top level of the built or unbuilt source directory. It may

be invoked with no arguments; useful arguments include:

 uc

,

 us

Do not sign the

.changes

file or the source package

.dsc

file, respectively.

 p

sign command

Invoke sign command instead of finding

gpg

or

pgp

on the

PATH

. sign 

command must behave just like

gpg

or

pgp

.

 r

root command

When root privilege is required, invoke the command root command. root 

command should invoke its first argument as a command, from the

PATH

if necessary, and

pass its second and subsequent arguments to the command it calls. If no root command is

supplied then dpkg buildpackage will take no special action to gain root privilege, so that

for most packages it will have to be invoked as root to start with.

 b

,

 B

Two types of binary only build and upload   see

dpkg source(1)

.

C.1.3

dpkg gencontrol

  generates binary package control files

This program is usually called from

debian/rules

(see `The Debianised source tree' on

page

114

) in the top level of the source tree.

This is usually done just before the files and directories in the temporary directory tree where

the package is being built have their permissions and ownerships set and the package is con 

structed using

dpkg deb/

1

.

dpkg gencontrol

must be called after all the files which are to go into the package have

been placed in the temporary build directory, so that its calculation of the installed size of a

package is correct.

It is also necessary for

dpkg gencontrol

to be run after

dpkg shlibdeps

so that the vari 

able substitutions created by

dpkg shlibdeps

in

debian/substvars

are available.

For a package which generates only one binary package, and which builds it in

debian/tmp

relative to the top of the source package, it is usually sufficient to call

dpkg gencontrol

.

Sources which build several binaries will typically need something like:

1

This is so that the control file which is produced has the right permissions