]> git.ipfire.org Git - thirdparty/krb5.git/commitdiff
Upgrade from KfW betas, too
authorBen Kaduk <kaduk@mit.edu>
Mon, 13 Aug 2012 19:03:45 +0000 (15:03 -0400)
committerBen Kaduk <kaduk@mit.edu>
Wed, 29 Aug 2012 18:50:21 +0000 (14:50 -0400)
Instead of using 3.9.9 as a conditional for the maximum version to
upgrade from, just use the current version.
This seems to pick up beta tags properly (so we can upgrade
from, e.g., beta 6 to beta 7 using the installer's upgrade tools),
and is future-proof.

Note that a 64-bit installer will not pick up an existing 32-bit
install (or vice versa), but there does not seem to be infrastructure
to deal with this situation easily.
Also, "downgrading" by running an older installer with a newer version
already installed will cause both versions to be simultaneously
installed; only do this if you know what you're doing.

ticket: 7334 (new)
queue: kfw
target_version: 1.10.4
tags: pullup

src/windows/installer/wix/kfw.wxs

index 74ef8ac0cf0aa4f1dffb5aab23505a7512823e24..c7b86ac9ea7904b3fed8dea604ea18965e0bbedc 100755 (executable)
         
         <!-- KfW MSI -->
         <Upgrade Id="61211594-AAA1-4A98-A299-757326763CC7">
-            <UpgradeVersion IgnoreRemoveFailure="no" IncludeMinimum="no" Maximum="3.9.9" IncludeMaximum="yes" MigrateFeatures="yes" Property="UPGRADEKFW" />
+            <UpgradeVersion IgnoreRemoveFailure="no" IncludeMinimum="no" Maximum="$(var.VersionString)" IncludeMaximum="yes" MigrateFeatures="yes" Property="UPGRADEKFW" />
         </Upgrade>
        
         <!-- NSIS installation -->