Skip to content
Snippets Groups Projects
  • Simon Tatham's avatar
    4d8782e7
    Rework versioning system to not depend on Subversion. · 4d8782e7
    Simon Tatham authored
    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]
    4d8782e7
    History
    Rework versioning system to not depend on Subversion.
    Simon Tatham authored
    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]
mkunxarc.sh 1.12 KiB