Add criteria for using deltas to update docs.

I came here looking for this and didn't find it. :) The rationale I'm adding is based on this function, let me know if I'm interpreting it incorrectly:

f63edb85d2/src/Squirrel/UpdateInfo.cs (L76)
This commit is contained in:
Finn Ellis
2017-11-17 17:13:02 -08:00
committed by GitHub
parent 38834f7dbe
commit 8c513adee4

View File

@@ -7,7 +7,7 @@
The following steps are performed by the `UpdateManager` each time your app is executed:
1. **Check for Updates** - the `RELEASES` file at the distribution location is downloaded and compared to local `RELEASES` file to check for any updates.
2. **Download & Verify Update Packages** - if there is a new release, the `UpdateManager` determines whether to download the deltas or the latest full package to update to the current version. The packages are compared against their SHA1 in the `RELEASES` file for verification.
2. **Download & Verify Update Packages** - if there is a new release, the `UpdateManager` determines whether to download the deltas or the latest full package (by calculating which one requires less total downloading) to update to the current version. The packages are compared against their SHA1 in the `RELEASES` file for verification.
3. **Build Full Package from Deltas** - if delta packages were downloaded, a new full package is created from the previous full package and the downloaded delta file.
3. **Install New Version** - the current version of MyApp is extracted from the full package and placed in a new `%LocalAppData%\MyApp` install directory based on the version number (e.g., `app-1.0.1`).
4. **Update Shortcuts** - desktop and Windows Start Menu shortcuts are updated to point to the new MyApp version (via the `--processStart` command line parameter passed to `Update.exe`).