Change Details

For the Gpg4win (and related builds) we want * Kleopatra shows version of Gpg4win (or GPD, etc.) in About window * Kleopatra shows its version including the git revision in Components tab

For the Gpg4win (and related builds) we want * Kleopatra shows version of Gpg4win (or GPD, etc.) in About window * Kleopatra shows its version including the git revision in Components tab Open questions: * The manifest file currently uses description "GNU Privacy Guard (Kleopatra)", assemblyIdentity.name "GnuPG.kleopatra", and version `@kleopatra_version_win@.0`. * The versioninfo.rc file currently uses `@kleopatra_fileversion_win@` as FILEVERSION and PRODUCTVERSION. * The versioninfo.rc file currently uses `@kleopatra_version_win@` as FileVersion value and ProductVersion value. * kleopatra_version_win is the built-in 3-digit version number of kleopatra. * kleopatra_fileversion_win is a 4-digit comma-separated version number consisting of the built-in major, minor, and micro version and a 0. Shall these version numbers also match the Gpg4win version instead of the built-in kleopatra version?

For the Gpg4win (and related builds) we want * Kleopatra shows version of Gpg4win (or GPD, etc.) in About window * Kleopatra shows its version including the git revision in Components tab Open questions: * The manifest file currently uses description "GNU Privacy Guard (Kleopatra)", assemblyIdentity.name "GnuPG.kleopatra", and version `@kleopatra_version_win@.0`. * The versioninfo.rc file currently uses `@kleopatra_fileversion_win@` as FILEVERSION and PRODUCTVERSION. * The versioninfo.rc file currently uses `@kleopatra_version_win@` as FileVersion value and ProductVersion value. * kleopatra_version_win is the built-in 3-digit version number of kleopatra. * kleopatra_fileversion_win is a 4-digit comma-separated version number consisting of the built-in major, minor, and micro version and a 0. Shall these version numbers also match the Gpg4win version instead of the built-in kleopatra version?