On Sat, 07 May 2011 at 13:33:53 +0200, Enrico Weigelt wrote:
> c) does _NOT_ call configure
As much as I wish this had been the convention, it isn't - the convention is
that autogen.sh *does* call ./configure (often with options suitable for
developers of the project, whereas the ./configure defaults are more suitable
for packagers). Not doing so will just confuse people (and build systems
like jhbuild, for that matter). It's mainly intended to be used to get
started with development from a VCS checkout.
Many upstreams do provide some way to not run ./configure (something like
"./autogen.sh --no-configure" or "NOCONFIGURE=1 ./autogen.sh").
For many (most? all?) autoconf/automake projects, running "autoreconf" is
enough; that's essentially what dh_autoreconf does.
S
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20110507230300.ga7...@reptile.pseudorandom.co.uk
