| Age | Commit message (Collapse) | Author |
|---|
|
We don't install low-level system components that have potential of
ruining the system, which would be the reason to create the restore
points. Some systems suffer from very long creation of the restore
points, like in tdf#129087:
...
MSI (s) (60:00) [09:18:54:201]: Calling SRSetRestorePoint API. dwRestorePtType: 1, dwEventType: 102, llSequenceNumber: 0, szDescription: "Removed LibreOffice 6.3 Help Pack (English (United Kingdom))".
MSI (s) (60:00) [09:26:57:699]: The call to SRSetRestorePoint API succeeded. Returned status: 0, llSequenceNumber: 73.
...
So let's just disable the generation of restore points, as per [1].
[1] https://docs.microsoft.com/en-us/windows/win32/msi/msifastinstall
Change-Id: I452859d72284e0b2ea9a407e30a5e256a8c0a0f6
Reviewed-on: https://gerrit.libreoffice.org/84113
Tested-by: Jenkins
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
|
|
section.
The OOO_ARPURLINFOABOUTTEMPLATE is simply missleading as the caption in
Windows itself is "Supportlink". As the help states that the product
homepage can be used, switch to libreoffice.org, see documentation at
https://msdn.microsoft.com/en-us/library/aa367752
Additionally switch some links to https.
Change-Id: I8d6d871130d2a50a5ce9aa3e80687601e3038c4e
Reviewed-on: https://gerrit.libreoffice.org/52193
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
|
|
OLDPRODUCT2 - it was a workaround for OOo 1.9, obsolete
SAMEPRODUCTS - same product have the same ProductCode, so installer detect it
anyway under normal circumstances. It is possible that a tester/developer tries
to install the same version with different ProductCode over an existing installation
(e.g. dailyes or RCs). Then we are in trouble. However, SAMEPRODUCTS was not in use.
Moreover, Windows Installer uses only the first three fields of the product version.
So we cannot make difference between e.g. 4.0.3.1 and 4.0.3.2, and this is the new versioning
scheme.
BETAPRODUCTS - LibreOffice have never used different upgrade code (BETAUPGRADECODE) for betas.
OLDPRODUCTSPATCH, SAMEPRODUCTSPATCH, NEWPRODUCTSPATCH - related to old Star Division patching
mechanism, they were commented out anyway.
STUBPRODUCTS, STUBUPGRADECODE - these look useless
Change-Id: I77d67b72e18fa6b3ba4182b99e198c42f247cea4
|
|
Change-Id: Ib2dc00c024762800fdb74ffb376d92a8583d44ad
|
|
2008/08/21 15:14:01 is 1.4.62.1: #i92952# ooo3 has to remove all older ooo3 products
|
|
2008/05/15 09:06:14 is 1.3.208.1: #i42871# translation for Windows Installer dialog titles
|
|
2007/03/05 16:48:39 is 1.2.208.1: #145483# removing errors in msi databases
|
|
2005/09/08 10:44:44 is 1.1.2.1: #120096# new sdkoo product
|
