第 16 章 debmake options

目录

16.1. Shortcut option (-i)
16.2. debmake -b
16.3. Snapshot upstream tarball
16.4. debmake -B
16.5. debmake -x

Here are some additional explanations for debmake options.

The debmake command offers a shortcut option.

  • -i:执行构建二进制包的脚本

前文中第 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 手册页中的相关一部分内容。

-b, --binaryspec "binarypackage[:type], …​"

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:

  • bin: C/C++ compiled ELF binary code package (any, foreign) (default, alias: "", i.e., null-string)
  • data: Data (fonts, graphics, …​) package (all, foreign) (alias: da)
  • dev:库开发软件包(any,same)(别名:de
  • doc:文档软件包(all,foreign)(别名:do
  • lib:库软件包(any,same)(别名:l
  • perl:Perl 脚本软件包(all,foreign)(别名:pl
  • python3: Python (version 3) script package (all, foreign) (alias: py3, python, py)
  • ruby:Ruby 脚本软件包(all,foreign)(别名:rb
  • nodejs:基于 Node.js 的 JavaScript 软件包(all,foreign)(别名:js
  • script: Shell and other interpreted language script package (all, foreign) (alias: sh)

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:

    • -b’foo:bin', or its short form -b'-', or no -b option
  • Generating an executable (python3) binary package python3-foo:

    • -b’python3-foo:py', or its short form -b’python3-foo'
  • Generating a data package foo:

    • -b’foo:data', or its short form -b'-:data'
  • Generating a executable binary package foo and a documentation one foo-doc:

    • -b’foo:bin,foo-doc:doc', or its short form -b'-:-doc'
  • Generating a executable binary package foo, a library package libfoo1, and a library development package libfoo-dev:

    • -b’foo:bin,libfoo1:lib,libfoo-dev:dev' or its short form -b'-,libfoo1,libfoo-dev'

如果源码树的内容和类型的设置不一致,debmake 命令会发出警告。

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 as:

[~] $ cd /path/to/upstream-vcs
[upstream-vcs] $ debmake -p package -i debuild

If the upstream VCS is hosted in the package/ directory instead of the upstream-vcs/ directory, the -p package can be skipped.

If the upstream source tree in the VCS contains the debian/* files, the debmake command with the -i option automates the making of a non-native Debian package from the VCS snapshot while using these debian/* files.

[upstream-vcs] $ dch
   ... update debian/changelog
[upstream-vcs] $ git add -A .; git commit -m "vcs with debian/*"
[upstream-vcs] $ debmake -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.12 节 “Quasi-native Debian packaging”” for more details.

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 命令不会修改任何已存在的配置文件。