mirror of
https://github.com/kovidgoyal/calibre.git
synced 2025-07-09 03:04:10 -04:00
MSI installer: Always re-install all files
This commit is contained in:
parent
3177772cc6
commit
a551136f5b
@ -11,10 +11,17 @@
|
|||||||
SummaryCodepage='1252' />
|
SummaryCodepage='1252' />
|
||||||
|
|
||||||
<Media Id="1" Cabinet="{app}.cab" CompressionLevel="{compression}" EmbedCab="yes" />
|
<Media Id="1" Cabinet="{app}.cab" CompressionLevel="{compression}" EmbedCab="yes" />
|
||||||
<!-- The following line ensures that DLLs are replaced even if their version is the same as before. This
|
<!-- The following line ensures that DLLs are replaced even if
|
||||||
is necessary because of the manifest nuking that was part of making calibre isolated. But I think it
|
their version is the same as before or they dont have
|
||||||
is more rigorous anyway. -->
|
versions. Microsoft's brain dead installer will otherwise
|
||||||
<Property Id='REINSTALLMODE' Value='emus'/>
|
use file dates to determine whether to install a file or
|
||||||
|
not. Simply not robust. And since we dont install any
|
||||||
|
system files whatsoever, we can never replace a system
|
||||||
|
file with an older version. This way the calibre install
|
||||||
|
should always result in a consistent set of files being
|
||||||
|
present in the installation folder, though of course, with
|
||||||
|
Microsoft there are no guarantees of anything. -->
|
||||||
|
<Property Id='REINSTALLMODE' Value='amus'/>
|
||||||
|
|
||||||
<Upgrade Id="{upgrade_code}">
|
<Upgrade Id="{upgrade_code}">
|
||||||
<UpgradeVersion Maximum="{version}"
|
<UpgradeVersion Maximum="{version}"
|
||||||
|
Loading…
x
Reference in New Issue
Block a user