Here are some additional explanations for debmake options.
The debmake command offers a shortcut option.
前文中“第 5 章 简单打包”的例子可以使用下面的命令直接达到目的。
[base_dir] $ debmake package-1.0.tar.xz -i debuild
![]() | 提示 |
|---|---|
|
A URL such as “https://www.example.org/DL/package-1.0.tar.xz” for a tarball, “https://github.com/username/package.git” for a git repository, or “/path/to/source_dir” for a local source tree may be used as an argument. |
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 命令会发出警告。
The debmake command invoked with the -B option can generate template files with .ex suffix. This is handy if you want to see auto-generated template files to the existing ones.
debmake 生成的模板文件数量由 -x[01234] 选项进行控制。
![]() | 注意 |
|---|---|
|
debmake 命令不会修改任何已存在的配置文件。 |