Add the manual page and be a bit quieter about making a distribution.

Makefile

@@ -1,23 +1,33 @@
 # Makefile for pgpcontrol to handle various maintenance functions.
 # $Id$
 
-VERSION = 2.0
+VERSION		= 2.0
+
+# Black magic to get the version and modification date arguments for pod2man
+# out of the comments in pgpverify and signcontrol.
+EXTRACT		= grep '^\# Version'
+REFORMAT	= sed -e 's/^\# Version /--release=/' -e 's/, / --date=/'
 
 # Generate a staging area to be copied to the FTP site.  This contains the
 # documentation and scripts separate, the .tar.gz file for the entire
 # distribution in a subdirectory, and the ARCHIVE area.
-dist: release
+dist: release pgpverify.8
 	mkdir -p staging
-	rsync -av ARCHIVE FORMAT README* pgpverify sample.control sign.sh \
-	    signcontrol staging/
+	rsync -a ARCHIVE FORMAT README* pgpverify pgpverify.8 \
+	    sample.control sign.sh signcontrol staging/
 	cp -p pgpcontrol-$(VERSION).tar.gz staging/
 
 # Generate a tarball of my entire working area, but without the archive of old
 # versions of the software.
-release:
+release: pgpverify.8
 	rm -f pgpcontrol-$(VERSION).tar.gz
 	mkdir -p pgpcontrol-$(VERSION)
-	rsync -C -av ./ pgpcontrol-$(VERSION)/
-	tar cfvz pgpcontrol-$(VERSION).tar.gz pgpcontrol-$(VERSION)
+	rsync -C -a ./ pgpcontrol-$(VERSION)/
+	rsync -a pgpverify.8 pgpcontrol-$(VERSION)/
+	tar cfz pgpcontrol-$(VERSION).tar.gz pgpcontrol-$(VERSION)
 	rm -rf pgpcontrol-$(VERSION)
 
+# Generate a pgpverify manual page using pod2man.
+pgpverify.8: pgpverify
+	pod2man `$(EXTRACT) pgpverify | $(REFORMAT)` \
+	    --section=8 --center="Maintenance Commands" pgpverify > $@