Julian Andres Klode wrote: > A 'debuild; debuild' should have a different result than a single > debuild then. If you build from a clean directory, the first build > will contain no changes. But after the build, the directory is not > clean anymore and debian/rules clean does not do enough to keep the > changes from appearing in the source package if you build again. >
I should have done that earlier (but didn't see the git repo, only now). I had a look at dh-autoreconf's code and the difference between what I do and what your script does is that I manually specify a list of files to "monitor" while you monitor all files. IMO, dh-autoreconf may be not specific to autoreconf but all same kind of tools and thus, can be enhanced by making, for example, the command to execute an argument which could be the command "true" (and keep "autoreconf" as a default) because, sometimes, it may be needed to make "debian/autoreconf.after" a bit later than just after executing "autoreconf". Hopefully, we can do that by overriding the file. If you have these options, dh-autoreconf becomes nothing more than a call to autoreconf if we have dh_backup (name proposed by buxy in the same thread). dh_backup can be integrated to debhelper and all that remains to be done is a call to "autoreconf" (depending on the implementation of dh_backup). -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
