Rework versioning system to not depend on Subversion.

I've shifted away from using the SVN revision number as a monotonic
version identifier (replacing it in the Windows version resource with
a count of days since an arbitrary epoch), and I've removed all uses
of SVN keyword expansion (replacing them with version information
written out by Buildscr).

While I'm at it, I've done a major rewrite of the affected code which
centralises all the computation of the assorted version numbers and
strings into Buildscr, so that they're all more or less alongside each
other rather than scattered across multiple source files.

I've also retired the MD5-based manifest file system. A long time ago,
it seemed like a good idea to arrange that binaries of PuTTY would
automatically cease to identify themselves as a particular upstream
version number if any changes were made to the source code, so that if
someone made a local tweak and distributed the result then I wouldn't
get blamed for the results. Since then I've decided the whole idea is
more trouble than it's worth, so now distribution tarballs will have
version information baked in and people can just cope with that.

[originally from svn r10262]

doc/Makefile

@@ -3,12 +3,12 @@ all: man index.html
 # Decide on the versionid policy.
 #
 # If the user has passed in $(VERSION) on the command line (`make
-# VERSION="Release 0.56"'), we use that as an explicit version
-# string. Otherwise, we use `svnversion' to examine the checked-out
-# documentation source, and if that returns a single revision
-# number then we invent a version string reflecting just that
-# number. Failing _that_, we resort to versionids.but which shows a
-# $Id for each individual file.
+# VERSION="Release 0.56"'), we use that as an explicit version string.
+# Otherwise, we use `svnversion' to examine the checked-out
+# documentation source, and if that returns a single revision number
+# then we invent a version string reflecting just that number. Failing
+# _that_, we resort to versionids.but which gives 'version
+# unavailable'.
 #
 # So here, we define VERSION using svnversion if it isn't already
 # defined ...

doc/blurb.but

@@ -1,5 +1,3 @@
-\define{versionidblurb} \versionid $Id$
-
 \define{dash} \u2013{-}
 
 \title PuTTY User Manual

doc/chm.but

@@ -20,4 +20,3 @@
 
 \cfg{html-head-end}{<link rel="stylesheet" type="text/css" href="chm.css">}
 
-\versionid $Id$

doc/config.but

@@ -1,5 +1,3 @@
-\define{versionidconfig} \versionid $Id$
-
 \C{config} Configuring PuTTY
 
 This chapter describes all the \i{configuration options} in PuTTY.

doc/errors.but

@@ -1,5 +1,3 @@
-\define{versioniderrors} \versionid $Id$
-
 \C{errors} Common \i{error messages}
 
 This chapter lists a number of common error messages which PuTTY and

doc/faq.but

@@ -1,5 +1,3 @@
-\define{versionidfaq} \versionid $Id$
-
 \A{faq} PuTTY \i{FAQ}
 
 This FAQ is published on the PuTTY web site, and also provided as an

doc/feedback.but

@@ -1,5 +1,3 @@
-\define{versionidfeedback} \versionid $Id$
-
 \A{feedback} \ii{Feedback} and \i{bug reporting}
 
 This is a guide to providing feedback to the PuTTY development team.

doc/gs.but

@@ -1,5 +1,3 @@
-\define{versionidgs} \versionid $Id$
-
 \C{gs} Getting started with PuTTY
 
 This chapter gives a quick guide to the simplest types of

doc/index.but

@@ -1,5 +1,3 @@
-\define{versionidindex} \versionid $Id$
-
 \IM{Unix version} Unix version of PuTTY tools
 \IM{Unix version} Linux version of PuTTY tools
 

doc/intro.but

@@ -1,5 +1,3 @@
-\define{versionidintro} \versionid $Id$
-
 \C{intro} Introduction to PuTTY
 
 PuTTY is a free SSH, Telnet and Rlogin client for 32-bit Windows

doc/licence.but

@@ -1,5 +1,3 @@
-\define{versionidlicence} \versionid $Id$
-
 \A{licence} PuTTY \ii{Licence}
 
 PuTTY is \i{copyright} 1997-2014 Simon Tatham.

doc/pageant.but

@@ -1,5 +1,3 @@
-\define{versionidpageant} \versionid $Id$
-
 \C{pageant} Using \i{Pageant} for authentication
 
 \cfg{winhelp-topic}{pageant.general}

doc/pgpkeys.but

@@ -1,5 +1,3 @@
-\define{versionidpgpkeys} \versionid $Id$
-
 \A{pgpkeys} PuTTY download keys and signatures
 
 \cfg{winhelp-topic}{pgpfingerprints}

doc/plink.but

@@ -1,5 +1,3 @@
-\define{versionidplink} \versionid $Id$
-
 \C{plink} Using the command-line connection tool \i{Plink}
 
 \i{Plink} (PuTTY Link) is a command-line connection tool similar to

doc/pscp.but

@@ -1,5 +1,3 @@
-\define{versionidpscp} \versionid $Id$
-
 \#FIXME: Need examples
 
 \C{pscp} Using \i{PSCP} to transfer files securely

doc/psftp.but

@@ -1,5 +1,3 @@
-\define{versionidpsftp} \versionid $Id$
-
 \C{psftp} Using \i{PSFTP} to transfer files securely
 
 \i{PSFTP}, the PuTTY SFTP client, is a tool for \i{transferring files}

doc/pubkey.but

@@ -1,5 +1,3 @@
-\define{versionidpubkey} \versionid $Id$
-
 \C{pubkey} Using public keys for SSH authentication
 
 \H{pubkey-intro} \ii{Public key authentication} - an introduction

doc/sshnames.but

@@ -1,5 +1,3 @@
-\define{versionidsshnames} \versionid $Id$
-
 \A{sshnames} SSH-2 names specified for PuTTY
 
 There are various parts of the SSH-2 protocol where things are specified

doc/udp.but

@@ -3,8 +3,6 @@
 \# PuTTY's `unwritten design principles'. It has nothing to do with
 \# the User Datagram Protocol.
 
-\define{versionidudp} \versionid $Id$
-
 \A{udp} PuTTY hacking guide
 
 This appendix lists a selection of the design principles applying to

doc/using.but

@@ -1,5 +1,3 @@
-\define{versionidusing} \versionid $Id$
-
 \C{using} Using PuTTY
 
 This chapter provides a general introduction to some more advanced

doc/vids.but

@@ -1,36 +1,4 @@
-\# Invoke the versionid macros defined in all the other manual
-\# chapter files.
+\# Fallback versionid for use when the build system hasn't provided a
+better one.
 
-\versionidblurb
-
-\versionidintro
-
-\versionidgs
-
-\versionidusing
-
-\versionidconfig
-
-\versionidpscp
-
-\versionidpsftp
-
-\versionidplink
-
-\versionidpubkey
-
-\versionidpageant
-
-\versioniderrors
-
-\versionidfaq
-
-\versionidfeedback
-
-\versionidlicence
-
-\versionidudp
-
-\versionidpgpkeys
-
-\versionidindex
+\versionid no version information available