| 第 16 章 debmake options | ||
|---|---|---|
 |
||
| 第 16 章 debmake options | ||
|---|---|---|
| |
||
目录
Here are some additional explanations for debmake options.
debmake 命令提供了两个快捷选项。
前文中“第 5 章 简单打包”的例子可以使用下面的命令直接达到目的。
$ debmake -a package-1.0.tar.gz -i debuild
![[提示]](images/tip.png) | 提示 |
|---|---|
|
A URL such as “https://www.example.org/DL/package-1.0.tar.gz” may be used for the -a option. |
| 提示 |
|---|---|
|
A URL such as “https://arm.koji.fedoraproject.org/packages/ibus/1.5.7/3.fc21/src/ibus-1.5.7-3.fc21.src.rpm” may be used for the -a option, too. |
The debmake command with the -b option provides an intuitive and flexible method to create the initial template debian/control file. This file defines the split of the Debian binary packages with the following stanzas:
The debmake command also sets an appropriate set of substvars (substitution variables) used in each pertinent dependency stanza.
我们在这里直接引用 debmake 手册页中的相关一部分内容。
set the binary package specs by a comma separated list of binarypackage:type pairs. Here, binarypackage is the binary package name, and the optional type is chosen from the following type values:
The pair values in the parentheses, such as (any, foreign), are the Architecture and Multi-Arch stanza values set in the debian/control file. In many cases, the debmake command makes good guesses for type from binarypackage. If type is not obvious, type is set to bin.
Here are examples for typical binary package split scenarios where the upstream Debian source package name is foo:
Generating an executable binary package foo:
Generating an executable (python3) binary package python3-foo:
Generating a data package foo:
Generating a executable binary package foo and a documentation one foo-doc:
Generating a executable binary package foo, a library package libfoo1, and a library development package libfoo-dev:
如果源码树的内容和类型的设置不一致，debmake 命令会发出警告。
debmake 命令在带上 -cc 选项时可以向标准输出打印整个源码树的版权和许可证概要信息。
$ tar -xvzf package-1.0.tar.gz $ cd package-1.0 $ debmake -cc | less
如果转而使用 -c 选项，程序将提供较短的报告。
This test building scheme is suitable for git repositories organized as described in gbp-buildpackage(7), which uses the master, upstream, and pristine-tar branches.
The upstream snapshot from the upstream source tree in the upstream VCS can be made with the -d option if the upstream supports the “make dist” equivalence.
$ cd /path/to/upstream-vcs $ debmake -d -i debuild
除此之外，也可使用 -t 选项以使用 tar 命令生成上游源码包。
$ cd /path/to/upstream-vcs $ debmake -p package -t -i debuild
Unless you provide the upstream version with the -u option or with the debian/changelog file, a snapshot upstream version is generated in the 0~%y%m%d%H%M format, e.g., 0~1403012359, from the UTC date and time.
If the upstream VCS is hosted in the package/ directory instead of the upstream-vcs/ directory, the “-p package” can be skipped.
如果版本控制系统中的上游源码树包含了 debian/* 文件，debmake 命令在带有 -d 选项或者 -t 选项并结合 -i 选项可以自动化进行使用这些 debian/* 文件从版本控制系统快照中构建非原生软件包的流程。
$ cp -r /path/to/package-0~1403012359/debian/. /path/to/upstream-vcs/debian $ dch ... update debian/changelog $ git add -A .; git commit -m "vcs with debian/*" $ debmake -t -p package -i debuild
This non-native Debian binary package building scheme without the real upstream tarball is considered a quasi-native Debian package. See “第 11.13 节 “Quasi-native Debian packaging”” for more details.
这是测试性功能。
生成多个二进制软件包通常比只生成一个二进制软件包需要投入更多的工作量。对源码包进行测试构建是其中的必要一环。
例如，我们考虑将相同的 package-1.0.tar.gz（参见 “第 5 章 简单打包”）打包并生成多个二进制软件包。
调用 debmake 命令并使用 -j 选项以测试构建并报告结果。
$ debmake -j -a package-1.0.tar.gz
调用 debmake 命令以开始准备打包信息。
$ rm -rf package-1.0 $ tar -xvzf package-1.0.tar.gz $ cd package-1.0 $ debmake -b"package1:type1, ..."
使用 debuild 或等效的其它工具构建 Debian 软件包。
$ debuild
![[注意]](images/note.png) | 注意 |
|---|---|
|
The -j option for the debmake command invokes dpkg-depcheck(1) to run debian/rules under strace(1) to obtain library dependencies. Unfortunately, this is very slow. If you know the library package dependencies from other sources such as the SPEC file in the source, you may just run the "debmake …" command without the -j option and run the “debian/rules install” command to check the install paths of the generated files. |
这是测试性功能。
在使用上游新发行版本更新软件包时，debmake 可以使用已有的 debian/copyright 文件和整个更新的源码树文件进行对比验证版权和许可证信息。
$ cd package-vcs $ gbp import-orig --uscan --pristine-tar ... update source with the new upstream release $ debmake -k | less
The “debmake -k” command parses the debian/copyright file from the top to the bottom and compares the license of all the non-binary files in the current package with the license described in the last matching file pattern entry of the debian/copyright file.
在您编辑自动生成的 debian/copyright 文件时，请确保将最通用的文件匹配模式放在文件前部，最精确的匹配模式放在后部。
| 提示 |
|---|---|
|
For all new upstream releases, run the “debmake -k” command to ensure that the debian/copyright file is current. |
调用 debmake 命令并带上 -P 选项将会严厉地检查所有自动生成文件的版权和许可证文本信息；即使它们都使用宽松的许可证也是如此。
此选项不止会影响正常执行过程中所生成的 debian/copyright 文件的内容，也会影响带参数 -k、-c、-cc 和 -ccc 选项的输出内容。
debmake 生成的模板文件数量由 -x[01234] 选项进行控制。
| 注意 |
|---|---|
|
debmake 命令不会修改任何已存在的配置文件。 |
| |
||
| 第 15 章 debmake(1) 手册页 |
|