Chapter 2. Overview

The Debian packaging of the package-1.0.tar.gz, containing a simple C source following the “GNU Coding Standards” and “FHS”, can be done with the debmake command as follows.

 $ tar -xvzf package-1.0.tar.gz
 $ cd package-1.0
 $ debmake
   ... Make manual adjustments of generated configuration files
 $ debuild

If manual adjustments of generated configuration files are skipped, the generated binary package lacks meaningful package description but still functions well under the dpkg command to be used for your local deployment.

	Caution
	The debmake command only provides decent template files. These template files must be manually adjusted to their perfection to comply with the strict quality requirements of the Debian archive, if the generated package is intended for general consumption.

If you are new to Debian packaging, focus on understanding the overall process rather than worrying about the details.

If you are familiar with Debian packaging, you’ll notice that debmake is similar to the dh_make command. This is because debmake is designed to replace the functionality historically provided by dh_make. ^[3]

The debmake command is designed with the following features:

The debmake command delegates most of the heavy lifting to its back-end packages: debhelper, dpkg-dev, devscripts, sbuild, schroot, etc.

	Tip
	Ensure that you properly quote the arguments of the -b, -f, -l, and -w options to protect them from shell interference.

	Tip
	The non-native Debian package is the normal Debian package.

	Tip
	The detailed log of all the package build examples in this document can be obtained by following the instructions in “Section 14.14, “Details””.

	Note
	The generation of the debian/copyright file, and the outputs from the -c (see “Section 16.3, “debmake -cc””) and -k (see “Section 16.6, “debmake -k””) options involve heuristic operations on the copyright and license information. They may produce some erroneous results.