Package: autotools-dev
Version: 20041130.2
Severity: wishlist
Tags: patch
Hi, I liked your debian-mentor message. I think adding it to your
README.Debian makes it much more clear. (I put few extra hints in
maint-guide CVS so people will read autotools-dev README.Debian.)
Here is patch to the current unstable source.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
-- no debconf information
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[EMAIL PROTECTED]> Brussels Belgium, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
diff -Nru autotools-dev-20041130.2-orig/debian/README.Debian
autotools-dev-20041130.2/debian/README.Debian
--- autotools-dev-20041130.2-orig/debian/README.Debian 2004-11-15
14:40:06.000000000 +0100
+++ autotools-dev-20041130.2/debian/README.Debian 2005-01-15
09:39:41.000000000 +0100
@@ -2,10 +2,32 @@
$Id: README.Debian,v 1.21 2004/11/15 13:40:06 hmh Exp $
--------------------------------------------------------
+Basics:
+You have two good choices, and one bad choice for packaging upstream source
+which uses automake and autoconf and contains generated files:
+
+ 1. Tolerate the big diff size, and run the autotools stuff before you
+ create the debian source package. This is what I usually do. If
+ you do this, go read the following section.
+
+ 2. Patch the autotools files (*.in, *.am) at build time, make sure all the
+ build dependencies are 100% correct (hint: conflicting with
+ autoconf2.13 is *always* a good idea if you're not using autoconf 2.13
+ and automake 1.4). This means that the autobuilders will have to rerun
+ the entire thing, and so will the users, etc.
+
+ When you're doing a full dpatch-based packaging, this choice makes
+ sense.
+
+ 3. Live with whatever crap upstream used. You do *not* have this choice
+ if libtool is being used, BTW. And it is a bad choice IMHO, I'm yet
+ to see any distribution with better autoconf, automake, libtool and
+ gettext packages than Debian. (I do have a lot of experience on this :P
+ but strongly discourage to do this. Bad choice.)
+
(Before packaging something in Debian that uses GNU autoconf, you must read the
"Introduction" and the "Calling GNU configure properly" sections)
-
Note: libtool is part of the autotools toolchain. We don't cover libtool in
this document, but there is one big fat warning that I will repeat here:
@@ -13,6 +35,7 @@
from Debian, or libtool 1.6 from upstream. If your package is using an older
libtool, upgrade immediately. See the libtool package for more information.
+=============================================================================
Introduction:
-------------
