Am 04.02.2010 21:29, schrieb Julian Andres Klode:
Anyway, this approach should allow us to build packages including
autoreconf with a simple
%:
dh --with autoreconf $@
debian/rules file which would be great. If you don't want to libtoolize,
and the package includes the libtool macros (ltversion, etc.) you could
even do an "export LIBTOOLIZE := true" in rules, so autoreconf calls
true instead of libtoolize.
Julien, I've got one thing to add to your scripts. You just check for
files that have been changed during autoreconf and remove them.
However, in most (all?) cases the directory autom4te.cache will be
created by autoreconf. Since I haven't found it to be of any use after
the autoreconf invocation, I suggest to remove it afterwards:
--- dh_autoreconf.orig
+++ dh_autoreconf
@@ -29,6 +29,7 @@
# Run autoreconf to recreate the needed files.
doit('autoreconf', '-f', '-i');
+doit('rm', '-f', '-r', 'autom4te.cache');
# Create a list of all the files (compared later on)
complex_doit('find -type f | xargs md5sum > debian/autoreconf.after');
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
