Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
MARK? Advanced Update mechanism suggestion (file-level CRC & updates etc.)
TomTester
New
Mark,
Recent upgrade instructions (1.1.1 -> 1.1.2) direct user to upgrade on file level as opposed to directory-level.
Upgrading the "minimal file set" is best solution when people 'mod' original release files, but a little cumbersome.
I've seen several bug reports that were the result of sloppiness (someone forgot to copy one file).
A more granular update check of vanilla-core could prevent many of these and make the process easier for less
technically inclined people (which would benefit the growth potential of Vanilla)
How difficult is this approach?
Pre-requisite: all official vanilla core release files contain a calculated CRC in the header (HCRC)
#1 - COLLECT
#2 - COMPARE
#3 - SELECT
#4a - DOWNLOAD
#4b - FUTURE: INSTALL
Recent upgrade instructions (1.1.1 -> 1.1.2) direct user to upgrade on file level as opposed to directory-level.
Upgrading the "minimal file set" is best solution when people 'mod' original release files, but a little cumbersome.
I've seen several bug reports that were the result of sloppiness (someone forgot to copy one file).
A more granular update check of vanilla-core could prevent many of these and make the process easier for less
technically inclined people (which would benefit the growth potential of Vanilla)
How difficult is this approach?
Pre-requisite: all official vanilla core release files contain a calculated CRC in the header (HCRC)
#1 - COLLECT
collect installed files list and CRC in header from user's server
retrieve list of file/CRC combos for latest release from Lussumo server
#2 - COMPARE
process list of installed files
a. if filename NOT in core release -> flag as 'custom' & skip (listing optional)
b. if in core release -> calculate CRC of installed file (CCRC)
compare CCRC with HCRC of installed file
if NOT the same -> file was modded -> flag 'user-modified', update optional (check box NOT set)
if the same -> this is an original file
COMPARE CCRC with HCRC of latest release version matching filename
if the same -> no update available, don't list
if different -> flag 'updated' and add update (check box IS set)
#3 - SELECT
- user reviews files to be included in download package using check boxes,
selection of updates to MODDED files allowed
#4a - DOWNLOAD
- user clicks 'update' and custom package is generated and sent as download
#4b - FUTURE: INSTALL
- put board in 'maintenance mode'
- back up files in download package to 'fall-back' install
- auto-update files
- in case of failure, user can revert to 'fall-back' install
0
This discussion has been closed.
Comments
I do like the idea though