272
edits
| Line 29: | Line 29: | ||
Once the XPI has been completely downloaded, it's signature will be verified. If the signature checks out, then assuming that Firefox has permission from the user, it will install the XPI. The XPI will have a very simple install.js file that will copy the upgrade executable into the correct location within the Firefox installation directory. | Once the XPI has been completely downloaded, it's signature will be verified. If the signature checks out, then assuming that Firefox has permission from the user, it will install the XPI. The XPI will have a very simple install.js file that will copy the upgrade executable into the correct location within the Firefox installation directory. | ||
==Processing the | ==Processing the Update== | ||
At startup, Firefox will look for an update executable in a fixed location. If it finds the executable, then assuming it has permission from the user it will launch the update executable and exit. Once the | At startup, Firefox will look for an update executable in a fixed location. If it finds the executable, then assuming it has permission from the user it will launch the update executable and exit. Once the update executable determines that Firefox has exited, it will begin applying the updates. | ||
Before making any changes to the existing Firefox installation, the update executable will scan all files to be modified and verify that they are the expected version. If it finds that any files are not in sync with what it expects to find, then it will not apply the update. Otherwise, it will proceed to either: add, remove, replace, or patch existing files. | Before making any changes to the existing Firefox installation, the update executable will scan all files to be modified and verify that they are the expected version. If it finds that any files are not in sync with what it expects to find, then it will not apply the update. Otherwise, it will proceed to either: add, remove, replace, or patch existing files. | ||
edits