On Fri, Nov 16, 2018 at 2:26 AM Yavor Doganov <ya...@gnu.org> wrote: > > Using autoreconf is part of the solution. Usually though, autoreconf > > prefers macros in the source over system copies. So if your source still > > contains the (outdated) copy, autoreconf will prefer it. > > That's not true if autoreconf is being run with the --force option > (which dh_autoreconf does); all files are considered obsolete then.
In my experience, Helmut is right. So in some of my packages, I've been adding the autoconf macros to Files-Excluded so that they aren't part of the Debian source when importing new tarball releases to ensure we actually build from the latest sources instead of sometimes ancient macros. Fortunately, many of my packages have switched to meson which at least doesn't have this issue. (I guess meson has some other cross-compiling issues currently but hopefully those will get straightened out soon.) Thanks, Jeremy Bicha
