Глава 8. Sanitization of the source

This method is suitable for avoiding non-https://www.debian.org/social_contract.html#guidelines[DFSG] compliant content in the upstream source tarball.

See «COPYRIGHT FILE EXAMPLES» in mk-origtargz(1).

This method is suitable for avoiding auto-generated files by removing them in the "debian/rules clean" target.

	Примечание
	The "debian/rules clean" target is called before the "dpkg-source --build" command by the dpkg-buildpackage command. The "dpkg-source --build" command ignores removed files.

This is for the non-native Debian package.

The problem of extraneous diffs can be fixed by ignoring changes made to specific parts of the source tree. This is done by adding the "extend-diff-ignore=…​" line in the debian/source/options file.

debian/source/options to exclude the config.sub, config.guess and Makefile files: 

# Don't store changes on autogenerated files
extend-diff-ignore = "(^|/)(config\.sub|config\.guess|Makefile)$"

	Примечание
	This approach always works, even when you can’t remove the file. It saves you from having to make a backup of the unmodified file just to restore it before the next build.

	Подсказка
	If you use the debian/source/local-options file instead, you can hide this setting from the generated source package. This may be useful when local non-standard VCS files interfere with your packaging.

This is for the native Debian package.

You can exclude certain files in the source tree from the generated tarball by adjusting the file glob. Add the "tar-ignore=…​" lines in the debian/source/options or debian/source/local-options files.

Примечание

For example, if the source package of a native package needs files with the .o extension as part of the test data, the setting in «Раздел 4.5, «devscripts setup»» may be too aggressive. You can work around this by dropping the -I option for DEBUILD_DPKG_BUILDPACKAGE_OPTS in «Раздел 4.5, «devscripts setup»» and adding the "tar-ignore=…​" lines in the debian/source/local-options file for each package.

The problem of extraneous content in the second build can be avoided by restoring the source tree. This is done by committing the source tree to the Git repository before the first build.

You can restore the source tree before the second package build. For example:

 $ git reset --hard
 $ git clean -dfx