debian-binary: deb檔案格式的版本, " 2.0\n" ▶ control.tar.gz: 描述套件相關資訊的檔案 control, md5sums, (pre|post)(rm|inst), triggers, shlibs, . . . ▶ data.tar.gz: 套件裡的資料 ▶ 你可以手動製作 .deb 檔案 http://tldp.org/HOWTO/html_single/Debi 開發必需之工具 ▶ 一台能以 root 權限存取的 Debian (or Ubuntu) 系統 ▶ 一些必需套件: ▶ build-essential: 和 Debian 套件有相依性並假定已安裝在開發者的機 器上 (不需在套件中的 control 欄位特別指定 Build-Depends: ) ▶ 相依 dpkg-dev 套件, 其中包含基本 Debian 特定工具, 以便於製 作 Debian 上傳(dput) Debian 套件打包教學指南 9 / 90 範例: 重包 dash 套件 1 安裝重包 dash 套件所需的必要套件以及 devscripts 套件 sudo apt-get build-dep dash (需要將deb-src 設定到 /etc/apt/sources.list) sudo apt-get install --no-install-recommends devscripts

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful