-EXTRA_DIST = GNUmakefile Makefile.cfg Makefile.maint \
- OChangeLog PACKAGING \
- djgpp/CVS djgpp/Makefile.maint djgpp/README.in \
- djgpp/config.bat djgpp/config.sed djgpp/config.site \
- djgpp/config_h.sed djgpp/subpipe.c djgpp/subpipe.h
+EXTRA_DIST = .prev-version .version \
+ cfg.mk ChangeLog-1998 ChangeLog-2012 PACKAGING \
+ djgpp/Makefile.maint djgpp/README.in djgpp/config.bat \
+ djgpp/config.sed djgpp/config.site djgpp/config_h.sed \
+ djgpp/subpipe.c djgpp/subpipe.h djgpp/djunpack.bat \
+ djgpp/fnchange.lst djgpp/testsuite.sed
+
+MAINTAINER_CHECKS = \
+ maintainer-check \
+ maintainer-push-check \
+ maintainer-xml-check \
+ maintainer-release-check
+.PHONY: $(MAINTAINER_CHECKS)
+$(MAINTAINER_CHECKS):
+ $(AM_V_GEN)cd tests && $(MAKE) $(AM_MAKEFLAGS) $@
+
+# See comments in build-aux/git-version-gen. However, we make .version depend
+# on configure so that .version and VERSION/PACKAGE_VERSION stay in sync in the
+# working copy (for example, when you run autoreconf && make). Allowing these
+# to fall out of sync appears to have little potential to improve Bison build
+# efficiency (even if we were to replace VERSION/PACKAGE_VERSION with .version
+# everywhere possible). On the other hand, it could be harmful. For example,
+# a developer might naively reference .version in a test case while the bison
+# executable still compiles with VERSION, and so the test case might fail or
+# pass incorrectly.
+BUILT_SOURCES = $(top_srcdir)/.version
+$(top_srcdir)/.version: configure
+ $(AM_V_GEN)echo $(VERSION) > $@-t && mv $@-t $@
+dist-hook: gen-ChangeLog
+ $(AM_V_GEN)echo $(VERSION) > $(distdir)/.tarball-version