Rationale for debmake
---------------------

debmake was created to address shortcomings of dh_make(1).

The initial targets:

 * make functioning binary packages directly with no user input
   - from upstream VCS (autotools, setup.py, ...)
     - setup.py means auto conversion from PyPI 
       https://pypi.python.org/pypi to Debian debs.
   - from upstream tarball
   - help migration from native to non-native package
   - multi-arch aware
 * make multi binary packages with flexible combinations
 * make packages with hardening turned on
 * efficient generation of debian/copyright
   - use licensecheck(1) but do more

The design guide line of debmake
--------------------------------

 * Keep it simple.
 * Use the new dh syntax.  (No cdbs.)
 * The basic ability of dh_make (and its predecessor deb-make) should be
   covered.  (debmake 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 multi-arch compatible ways.
 * The debmake command should not overwrite existing files by default.
 * The debmake command should not generate non-essential template files as default.

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
 * dh-make: 1998-2012 Craig Small <csmall@debian.org>
            command: dh_make

(debmake package has debmake as its command and start from version 4.0)

 -- Osamu Aoki <osamu@debian.org>  Sun, 12 Jan 2014 07:21:13 +0000
