summaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2007-10-22 19:54:52 +0200
committerJim Meyering <meyering@redhat.com>2007-10-28 15:29:01 +0100
commit441bb2a1c354b07da17ce0751fb9a41aa2cfdcbe (patch)
tree9b797f29db85e9187d4d6fcac9f4e0959f5a25c1 /README-hacking
parent0f345668724e79af9c89555a480c83ce7d7ed953 (diff)
downloadautoconf-441bb2a1c354b07da17ce0751fb9a41aa2cfdcbe.tar.gz
Make inter-release --version output more useful.
Now, each unofficial build has a version "number" like 2.61a-19-58dd, which indicates that it is built using the 19th change set (in _some_ repository) following the "v2.61a" tag, and that 58dd is a prefix of the commit SHA1. * build-aux/git-version-gen: New file. * configure.ac: Run it to set the version. (AM_INIT_AUTOMAKE): Don't check NEWS here. * Makefile.am (dist-hook): Arrange so that .version appears only in distribution tarballs, never in a checked-out repository. * .gitignore: Add .version here, too. Just in case. * tests/Makefile.am ($(srcdir)/package.m4): Depend on Makefile, not configure.ac, now that the version number changes automatically. Ensure that $(VERSION) is up to date for dist-related targets. * GNUmakefile: Arrange to rerun autoconf, if the version reported by git-version-gen doesn't match $(VERSION), but only for dist targets.
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking1
1 files changed, 1 insertions, 0 deletions
diff --git a/README-hacking b/README-hacking
index 0f0aa295..cbf27545 100644
--- a/README-hacking
+++ b/README-hacking
@@ -29,6 +29,7 @@ You can get a copy of the source repository like this:
The next step is to generate files like configure and Makefile.in:
+ $ cd autoconf
$ aclocal -I m4
$ automake
$ autoconf