1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
debmake for Debian
------------------
The debmake command is a helper script to generate basic Debian packaging files
using debhelper version 9 or newer with multiarch conscious way. See the
debmake(1) manpage in this package and the HTML documentation provided in the
debmake-doc package for more.
The debmake command is written in python and is intended to replace functions
traditionally offered by deb-make and dh_make commands.
This new debmake package has debmake as its command and starts its version from
4.0 to avoid version overlaps.
The author thanks previous efforts on this topic:
* debmake: 1996-1997 Christoph Lameter <clameter@debian.org>
1997-2006 Santiago Vila <sanvila@debian.org>
command: deb-make, version up to 3.8 (shell script)
* dh-make: 1998-2012 Craig Small <csmall@debian.org>
command: dh_make (perl script)
Rationale for debmake
---------------------
debmake was created to address shortcomings of dh_make(1): Notably:
* semi-automatic scanning of copyright
* flexible combination of binary package types
* multiarch aware
* friendly for the hardening of compiler flags
* almost automatic process from the upstream VCS (autotools, setup.py, ...)
* help upstream to manage the non-native package
The design guide line of debmake
--------------------------------
* Keep it simple.
* Use the new dh syntax. (No cdbs nor any make file inclusion system)
* The basic ability of dh_make (and its predecessor deb-make) should be
covered. (The debmake command intends to replace them.)
* The debmake command should require no or minimum arguments to do useful
things.
* The debmake command should help reviewing of the license for all source
files.
* The program structure should be friendly for adding the GUI.
* The native build system of the upstream source should be identified and
utilized.
* The debmake command should make it easy to create various combinations of
binary packages in the multiarch compatible way.
* The debmake command should not overwrite existing files by default.
* The debmake command should not generate non-essential template files as
default except for the first run in which normal template files are
generated.
-- Osamu Aoki <osamu@debian.org> Sun, 14 Dec 2014 17:11:26 +0000
|
