c16158772d
Renaming all README files for all top level modules to README.md, applying no content change at this stage to be able to track history of the files. These files should be edited to use correct Markdown syntax later. Change-Id: I542fa3f3d32072156f16eaad2211a397cc212665 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112977 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> |
||
|---|---|---|
| .. | ||
| inc | ||
| qa | ||
| source | ||
| workben | ||
| astyle.options | ||
| CustomTarget_generated.mk | ||
| Executable_mar.mk | ||
| Executable_mbsdiff.mk | ||
| Executable_test_updater_dialog.mk | ||
| Executable_update_service.mk | ||
| Executable_updater.mk | ||
| Makefile | ||
| Module_onlineupdate.mk | ||
| README.md | ||
| StaticLibrary_libmar.mk | ||
| StaticLibrary_libmarverify.mk | ||
| StaticLibrary_updatehelper.mk | ||
| WinResTarget_updater.mk | ||
Online update implementation based on Mozilla's MAR format + update mechanism
Parts of this code are copied from the mozilla repository, and adapted to LibreOffice needs:
firefox/modules/libmar -> onlineupdate/source/libmar firefox/toolkit/mozapps/update -> onlineupdate/source/update
The source/service directory contains the code for the silent windows updater that avoids the repeated administrator check for an update.
== NOTE == The updater executable should not depend on any other dynamic library in the LibreOffice installation as we would need to copy that one also to a temporary directory during update. We can't update any library or executable that is currently in use. For the updater executable we solve this problem by copying the updater before using it to a temporary directory.
On Windows we use the system to provide us with a crypto library whereas on Linux we use NSS.
== Update procedure ==
The updater executable is run two times. In a first run, the current installation is copied to a "update" directory and the update is applied in this "update" directory. During the next run, a replacement request is executed. The replacement request removes the old installation directory and replaces it with the content of the "update" directory.
=== User profile in the installation directory ===
The archive based installations have the user profile by default inside of the installation directory. During the update process this causes some problems that need special handling in the updater.
- The "update" directory is inside of the user profile resulting in recursive copying.
- During the replacement request the updater log is in the user profile, which changes location from the actual location to a backup location.