272
edits
Software Update:Processing Updates: Difference between revisions
no edit summary
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This document describes the process of applying updates once they have been downloaded. | |||
== Overview == | |||
At startup or shutdown, a routine called from XRE_main may perform the following steps to process pending updates: | |||
* Check for the existance of an "updates" folder in the main application folder. | * Check for the existance of an "updates" folder in the main application folder. | ||
| Line 8: | Line 10: | ||
* Mark the selected folder as ''applying''. | * Mark the selected folder as ''applying''. | ||
* Spawn the updater application to apply the selected update. | * Spawn the updater application to apply the selected update. | ||
* At this point, | * At this point, XRE_main exits. (NOTE: spawning the updater application may in fact mean that we call execv to load the updater image into the current process, but that is just an implementation detail.) | ||
* The updater takes over, applies the update (recording information to a log file for debugging purposes), and marks the update as either ''succeeded'' or ''failed''. | * The updater takes over, applies the update (recording information to a log file for debugging purposes), and marks the update as either ''succeeded'' or ''failed''. | ||
* The updater then launches | * The updater then (optionally) re-launches Firefox with a specified command line to resume execution. | ||
* Firefox performs any post-install work, including for example fixing up any Windows registry keys. | * Firefox then performs any post-install work, including for example fixing up any Windows registry keys. | ||
== Update Status == | == Update Status == | ||