2004-08-29 Gary V. Vaughan <gary@gnu.org>
+ * configure.ac: Bumped version to 1.9b.
+ * NEWS: Updated.
+ * INSTALL, config/config.guess, config/config.sub,
+ config/texinfo.tex: Updated from canonical source.
+ * Makefile.maint, HACKING: Update instructions for releasing in a
+ VPATH build.
+
* Makefile.am (dist-hook): Only run if README-alpha exists.
* README.alpha: Renamed from README-alpha to stop automake from
automatically adding it to DIST_COMMON.
+ install-sh
+ missing
The ones that are important for a release can be udated with,
- `make -fMakefile.maint fetch'.
+ `make -fMakefile.maint fetch' (or `make -f../Makefile.maint fetch'
+ if you are running from a VPATH build directory, where `../' is the
+ relative path to the directory with `configure' in it).
* Changes other than bug fixes must be mentioned in NEWS
keys will be registered on ftp-upload.gnu.org and only then will you be
authorized to upload files to the FSF ftp machines.
+* Make sure you have wget installed.
+
* Make sure you have a copy of xdelta installed, and a copy of the previous
release tarball in the build directory.
* Have some tea. If you are running on less than 3.6GHz CPU, order
a pizza too ;-)
-* Run ./configure and then make.
+* Run ./configure (or create a build directory first and run configure
+ from there, if you want to keep the build tree separate).
-* Run `make -fMakefile.maint fetch', which will fetch new versions of the
- files that are maintained outside of libtool.
+* Run `make -fMakefile.maint fetch' (or `make -f../Makefile.maint fetch'
+ if you are running from a VPATH build directory, where `../' is the
+ relative path to the directory with `configure' in it), which will
+ fetch new versions of the files that are maintained outside of
+ libtool.
-* Run ./commit.
+* Run `make distcheck'. If there are any problems, fix them and start
+ again.
+
+* Run ./commit from the source tree.
-* Run `make -fMakefile.maint cvs-dist' which will build a release tarball
- (with `make distcheck'), tag the tree with release-$(VERSION) and generate
- the gpg signature files.
+* Run `make -fMakefile.maint cvs-dist' (or `make -f../Makefile.maint
+ cvs-dist' if you are running from a VPATH build directory, where `../'
+ is the relative path to the directory with `configure' in it), which
+ will build a release tarball (with `make distcheck'), tag the tree
+ with release-$(VERSION) and generate the gpg signature files.
-* Run 'make -fMakefile.maint deltas' (pass LASTRELEASE=min.maj[.mic[alpha]]
- if needed) to create both diff and xdelta files between the previous
- release tarball and the new with detached gpg signature files and clear
- signed directive files.
+* Run 'make -f[../]Makefile.maint deltas' (pass
+ LASTRELEASE=min.maj[.mic[alpha]] if needed) to create both diff and
+ xdelta files between the previous release tarball and the new with
+ detached gpg signature files and clear signed directive files.
* Upload release tarball, diff file and xdelta file, plus their associated
detached gpg signature files and clear signed directive files to
release announcement.
* If not an alpha, replace manual.html with the new one
- (generate with `make -f Makefile.maint web-manual').
+ (generate with `make -f[../]Makefile.maint web-manual').
-## Makefile.maint -- Makefile rules for libtool maintainers
+## Makefile.maint -- Makefile rules for libtool maintainers -*-Makefile-*-
##
## Copyright (C) 2004 Free Software Foundation
##
# include the Makefile than figure out a way to put them in here too
include Makefile
Makefile:
- @echo " *** Source directory must be configured to use the "
- @echo " *** maintainer rules."
+ @echo " *** Run maintainer rules from the build tree, with"
+ @echo " *** \`make -f../Makefile.maint' for example, where"
+ @echo " *** \`../' is the relative path back to the directory"
+ @echo " *** that contains the \`Makefile.maint'. Alternatively,"
+ @echo " *** run `./configure' in the source tree for an in"
+ @echo " *** tree build."
@exit 1
TEXI2HTML = texi2html