> > Rob, do you have any idea about how to fix this?
>
> The only thing I've thought of so far is to change debian/rules to not
> rely on timestamps for this file. Instead keep a file of the md5sums
> of the *.dpatch files and use that and cmp to determine when to
> re-generate. i.e. (in psudeo-make code):
>
> define update_autofiles_diff_if_needed
> md5sum debian/*.dpatch > debian/tmp-dpatch.md5
> if ! cmp debian/dpatch.md5 debian/tmp-dpatch.md5; \
> then \
> $(update_debian_autofiles_diff); \
> md5sum debian/*.dpatch > debian/dpatch.md5; \
> fi
> endef
>
> Then I'd just have to arrange for this action to be taken at all the
> appropriate times. A bit ugly perhaps, but it looks like it might
> work.
To my mind, we should avoid to do this automatically from the makefile
and generate a dpatch manually every we have to regenerate the
configure script.
Currently, the only file which is modified when changing configure.in
is configure, so this should be straightforward.
Quoting Rob Browning <email address hidden>:
> > Rob, do you have any idea about how to fix this? autofiles_ diff_if_ needed tmp-dpatch. md5 tmp-dpatch. md5; \ debian_ autofiles_ diff); \
>
> The only thing I've thought of so far is to change debian/rules to not
> rely on timestamps for this file. Instead keep a file of the md5sums
> of the *.dpatch files and use that and cmp to determine when to
> re-generate. i.e. (in psudeo-make code):
>
> define update_
> md5sum debian/*.dpatch > debian/
> if ! cmp debian/dpatch.md5 debian/
> then \
> $(update_
> md5sum debian/*.dpatch > debian/dpatch.md5; \
> fi
> endef
>
> Then I'd just have to arrange for this action to be taken at all the
> appropriate times. A bit ugly perhaps, but it looks like it might
> work.
To my mind, we should avoid to do this automatically from the makefile
and generate a dpatch manually every we have to regenerate the
configure script.
Currently, the only file which is modified when changing configure.in
is configure, so this should be straightforward.
Cheers,
--
Jérôme Marant