章 9. More on packaging

All customization data for the Debian source package resides in the debian/ directory as presented in “節 5.7, “第三步：編輯模板檔案””:

When these are not sufficient to make a good Debian package, -p1 patches of debian/patches/* files are deployed to modify the upstream source. These are applied in the sequence defined in the debian/patches/series file before building the package as presented in “節 5.9, “Step 3 (alternatives): Modification to the upstream source””.

You should address the root cause of the Debian packaging problem in the least invasive way possible. This approach will make the generated package more robust for future upgrades.

	注意
	If the patch addressing the root cause is useful to the upstream project, send it to the upstream maintainer.

Flexible customization of the 節 6.5, “debian/rules file” is achieved by adding appropriate override_dh_* targets and their rules.

When a special operation is required for a certain dh_foo command invoked by the dh command, its automatic execution can be overridden by adding the makefile target override_dh_foo in the debian/rules file.

構建的過程可以使用某些上游提供的介面進行定製化，如使用傳遞給標準的原始碼構建系統的引數。這些構建系統包括但不限於：

In this case, you should add the override_dh_auto_build target with “dh_auto_build -- arguments”. This ensures that arguments are passed to the build system after the default parameters that dh_auto_build usually passes.

	提示
	Avoid executing bare build system commands directly if they are supported by the dh_auto_build command.

參見：

DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 ...
ifeq ($(DEB_HOST_ARCH_OS),linux)
CONFIGURE_FLAGS += --enable-wayland
endif

參見 “節 10.10, “多體系架構””、dpkg-architecture(1) 和 dpkg-buildflags(1)。

$ uscan
 ... foo-newversion.tar.gz downloaded
$ uupdate -v newversion ../foo-newversion.tar.gz

After the above, you should refresh debian/patches/* files (see “節 9.5, “Manage patch queue with dquilt””) and update debian/changelog with the dch(1) command.

When “debian uupdate” is specified at the end of line in the debian/watch file, uscan automatically executes uupdate(1) after downloading the tarball.

 $ sudo sbuild -d unstable

In schroot(1) terminology, this builds a Debian package in a clean ephemeral chroot “chroot:unstable-amd64-sbuild” started as a copy of the clean minimal persistent chroot “source:unstable-amd64-sbuild”.

This build environment was set up as described in “節 4.6, “sbuild setup”” with “sbuild-debian-developer-setup -s unstable” which essentially did the following:

 $ sudo mkdir -p /srv/chroot/dist-amd64-sbuild
 $ sudo sbuild-createchroot unstable /srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
 $ sudo usermod -a -G sbuild <your_user_name>
 $ sudo newgrp -

The schroot(1) configuration for unstable-amd64-sbuild was generated at /etc/schroot/chroot.d/unstable-amd64-sbuild.$suffix :

[unstable-amd64-sbuild]
description=Debian sid/amd64 autobuilder
groups=root,sbuild
root-groups=root,sbuild
profile=sbuild
type=directory
directory=/srv/chroot/unstable-amd64-sbuild
union-type=overlay

其中：

You can update this source chroot “source:unstable-amd64-sbuild” by:

 $ sudo sbuild-update -udcar unstable

You can log into this source chroot “source:unstable-amd64-sbuild” by:

 $ sudo sbuild-shell unstable

	提示
	If your source chroot filesystem is missing packages such as libeatmydata1, ccache, and lintian for your needs, you may want to install these by logging into it.

See dh_bugfiles(1) and “reportbug’s Features for Developers (README.developers)”

	提示
	如果您總是需要提醒提交報告的使用者某些注意事項或詢問他們某些問題，使用這些檔案可以將這個過程自動化。