This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Manifest structure
Patrick McCarty edited this page Nov 24, 2016
·
3 revisions
A SWUPD manifest is a structured text file with a header and a body. A blank line separates the header from the body. Each line of the header and body is composed of multiple tab-separated fields.
Each line in the header has 2 fields; the first is a keyword, and the second is a value. Accepted keywords are:
- MANIFEST: The first line of manifest (the "magic"). Second field indicates the format number used to create the manifest.
- version: The build version number for which the manifest was created.
- previous: The build version number indicating when the manifest last changed.
- filecount: The number of entries in the manifest body.
- timestamp: The time the manifest was created, in UNIX time.
- contentsize: The size in bytes of all files listed in the manifest body.
- includes: (optional) A separate bundle manifest to be included with this one (effectively a "parent" bundle). There may be multiple includes lines.
Each line in the body has 4 fields, as follows:
- Metadata: Available values are listed on a separate page.
- Hash: Described on a separate page.
- Version: The build version when the file/directory/symlink/manifest last changed.
- Name: For bundle manifests, the absolute path to the file/directory/symlink. For MoM manifests, the bundle name.