Software Update:Processing Updates: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 6: | Line 6: | ||
* Enumerate its subfolders and build a list sorted by folder name. | * Enumerate its subfolders and build a list sorted by folder name. | ||
* Select the first folder in the list that is marked as ''pending''. | * Select the first folder in the list that is marked as ''pending''. | ||
* Mark the selected folder as '' | * 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, firefox exits. | * At this point, firefox exits. | ||
* The updater takes over, applies the update (recording information to a log file for debugging purposes), and marks the update as either '' | * 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 firefox with a special command line flag to resume execution. | * The updater then launches firefox with a special command line flag to resume execution. | ||
* Firefox performs any post-install work, including for example fixing up any Windows registry keys. | * Firefox performs any post-install work, including for example fixing up any Windows registry keys. | ||
| Line 18: | Line 18: | ||
<dl> | <dl> | ||
<dt>pending</dt><dd>The update is ready to be applied</dd> | <dt>pending</dt><dd>The update is ready to be applied</dd> | ||
<dt> | <dt>applying</dt><dd>The update is being applied</dd> | ||
<dt> | <dt>succeeded</dt><dd>The update was successfully applied</dd> | ||
<dt>failed</dt><dd>The update could not be applied</dd> | <dt>failed</dt><dd>The update could not be applied</dd> | ||
</dl> | </dl> | ||
This information is recorded in a text file named ''update.status'' stored in each update folder. | This information is recorded in a text file named ''update.status'' stored in each update folder. | ||
Revision as of 05:10, 3 May 2005
Overview
During startup, Firefox will check for any updates that are ready to be applied and apply them. The process consists of the following:
- Check for the existance of an "updates" folder in the main application folder.
- Enumerate its subfolders and build a list sorted by folder name.
- Select the first folder in the list that is marked as pending.
- Mark the selected folder as applying.
- Spawn the updater application to apply the selected update.
- At this point, firefox exits.
- 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 firefox with a special command line flag to resume execution.
- Firefox performs any post-install work, including for example fixing up any Windows registry keys.
Update Status
As described above, each update will have a status associated with it. The states consist of the following:
- pending
- The update is ready to be applied
- applying
- The update is being applied
- succeeded
- The update was successfully applied
- failed
- The update could not be applied
This information is recorded in a text file named update.status stored in each update folder.