Package-building procedure

[Stig Sandbeck Mathisen]

Dag-Erling Smørgrav <des at linpro.no> writes:

> I would like to have the following items documented for each
> distribution we support (Debian, Fedora, OpenSUSE):
>
>  - assuming the only things that need changing are the version
>  number and the changelog, which files need to be updated for a new
>  release?

The file needed to be updated is debian/changelog.  The version number
of the generated package is taken from there.  It should also contain
an entry with:

 * New upstream release

There is a tool in the debian package "devscripts" which can be used
to add changelog entries with the correct magic format:

dch -v 1.0.5 "New upstream release"

(This will also rename the current directory to "varnish-1.0.5")

>  - assuming all you have is the release tarball and the necessary
>  build tools, which command(s) are needed to produce a binary
>  package?

To build a package without signing it with gnupg, and package via
"fakeroot", cd to the source directory, and use:

dpkg-buildpackage -us -uc -rfakeroot

The following files will be generated in the parent directory:

-rw-r--r--  1 ssm ssm     367 2007-05-21 06:46 varnish_1.0.4-1.dsc
-rw-r--r--  1 ssm ssm    1135 2007-05-21 06:48 varnish_1.0.4-1_i386.changes
-rw-r--r--  1 ssm ssm  198964 2007-05-21 06:48 varnish_1.0.4-1_i386.deb
-rw-r--r--  1 ssm ssm  703947 2007-05-21 06:46 varnish_1.0.4-1.tar.gz

-- 
Stig Sandbeck Mathisen, Linpro