Florian Weimer <f...@deneb.enyo.de> writes:
> * Russ Allbery:
>> It's an interesting question whether we should just force dh-autoreconf
>> in debhelper unless the package maintainer explicitly turns it off. It
>> would save me work, just as I've now been able to take overrides back
>> out of all of my packages now that dpkg defaults to xz compression.
>> But it would be disruptive, and some packages would definitely fail to
>> build afterwards.
> The correct long-term fix is to change autotools to check a list of
> well-known paths for more recent versions of the scripts and use them
> instead of what is provided in the package.
This doesn't regenerate the other files from scratch. This only addresses
config.{sub,guess}, which is only a small part of the problem. And if you
run autoreconf, that takes care of this update as well (at least most of
the time). I therefore don't think pursuing this is particularly useful,
and we should instead make this problem moot by using dh-autoreconf or
something similar.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87a9bjzm23....@windlord.stanford.edu
