Re: Autoreconfing guide
On Wed, Jul 16, 2014 at 1:14 AM, Wookey wrote:
> https://wiki.debian.org/Autoreconf
Please mention the need to Build-Depend on any packages containing .m4
files that are embedded in the orig.tar.gz. For example, a lot of
packages use macros from autoconf-archive and some -dev packages
contain macros.
I note there are still some upstreams who do not trust autoconf. For
example the e2fsprogs maintainer recently rejected my patch to remove
autotools cruft from the git repository. As a result of autoconf
changes, he copied part (AM_MKINSTALLDIRS) of the nls.m4 file into the
acinclude.m4 file.
I wonder if lintian should be mentioning dh-autoreconf as best
practice at info/pedantic level?
I also wonder if autotools upstream should move away from storing
artefacts in the orig.tar.gz. A better model might be to run autotools
on the build machine and have an option that is run on
new/normal/modern platforms to spit out a blob of
shell/VBScript/something for ancient/weird/legacy/different platforms.
Presumably anyone trying to build for old platforms also has access to
a modern platform. Anyone seen plans for something like that?
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: