Re: [PATCH 1/2] dist: automate the post-release web-manual update process

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 3/2/2009 2:25 PM:
> +
> +.PHONY: web-manual
> +web-manual:
> +     @cd '$(srcdir)/doc'; \
> +       $(SHELL) ../build-aux/gendocs.sh -o '$(abs_builddir)/doc/manual' \
> +          --email $(PACKAGE_BUGREPORT) $(PACKAGE) \
> +         "$(PACKAGE_NAME) - Core GNU utilities"

That last bit is package-specific.  Should we factor 'Core GNU utilities'
into a string supplied by cfg.mk?

> +
> +* Run ./configure && make maintainerclean

maintainer-clean

> +
> +* Ensure that the desired versions of autoconf, automake, bison, etc.
> +  are in your PATH.

should we mention HACKING for the complete list?

> +
> +* Run bootstrap, (assuming your local copy of gnulib is in /gnulib):
> +  ./bootstrap --gnulib-srcdir=/gnulib

Is it worth adding gnulib as a git submodule, so that you can freeze which
gnulib commit id is associated with the release?  For an example, bison
has taken that approach.

> +* Run the following to create release tarballs.  Your choice selects the
> +  corresponding upload-to destination in the emitted gnupload command.
> +
> +    # "TYPE" must be major, beta or alpha
> +    XZ_OPT=-9e make TYPE

Shouldn't XZ_OPT be folded into maint.mk?

> +    CVS_RSH=ssh \
> +    cvs -d:ext:address@hidden:/web/coreutils co coreutils
> +
> +  Be sure to "cvs add" any files that "cvs status" marks with "?".

'cvs add -ko', so that strings that would otherwise look like CVS keywords
are not inadvertently altered.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmspmQACgkQ84KuGfSFAYBA9QCgsmpUCYImlh+u/4T4gSmpda8r
0YsAoMflPOdfv8wmc/b7CfZ2DfTKTkQ3
=zEL6
-----END PGP SIGNATURE-----