Chapter 8. More on packaging

All customization data for the Debian source package resides in the debian/ directory as presented in “Section 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 “Section 5.9, “Step 3 (alternatives): Modification to the upstream source””.

您应当以引入最少修改的方式解决打包中出现的根本问题。所生成的软件包应当考虑到未来的更新需求并有一定的健壮性。

	Note
	如果补丁对上游有所帮助的话，也请将解决根本问题的补丁反馈给上游作者和维护者。

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

如果需要在 dh 命令调用某些特定的 dh_foo 命令时采取某些特别的操作，则任何自动执行的操作均可以被 debian/rules 中额外添加的 override_dh_foo 这样的 Makefile 目标所覆写。

构建的过程可以使用某些上游提供的接口进行定制化，如使用传递给标准的源代码构建系统的参数。这些构建系统包括但不限于：

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

	Tip
	Please try not to execute the 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

参见 “Section 9.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 “Section 8.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 “Section 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

	Tip
	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)”

	Tip
	如果您总是需要提醒提交报告的用户某些注意事项或询问他们某些问题，使用这些文件可以将这个过程自动化。