Installation dir consistency: Check the file integrety of all files in the installation directory
Categories
(Toolkit :: Application Update, task)
Tracking
()
People
(Reporter: mpohle, Assigned: mpohle)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidedi] )
Attachments
(2 files)
To check the consistency of the files in the installation directory, we need to:
- Determine a list of files that are expected to always be in the installation directory and are necessary to start Firefox.
- Determine at what point in the build process these files are their final version and will not be modified.
- Find a way to integrate the creation of hashes for these files into the build process.
- Add this file to the
.mar
files so that they are shipped with the next update.
Assignee | ||
Updated•27 days ago
|
Updated•27 days ago
|
Assignee | ||
Updated•26 days ago
|
Assignee | ||
Updated•26 days ago
|
Assignee | ||
Comment 1•15 days ago
|
||
Updated•14 days ago
|
Assignee | ||
Comment 2•14 days ago
|
||
This solution is more elegant than what
https://phabricator.services.mozilla.com/D236607 would have let to. I
think that it is also going to work with partial updates and the
upcoming change to use the zucchini compression. It deviates from the
spec in that it does not produce a .json
file, but I considered it the
cleanest solution, because it reuses so much code that we already have.
It is going to put a checksums file in all builds (not only updates, but
also the installer) and the file will not just contain an md5 checksum,
but three different types of checksums for each file. The file format is
plain text and can simply be parsed as tuples between at space and
newline.
Updated•14 days ago
|
Updated•13 days ago
|
Updated•12 days ago
|
Description
•