Update packets are used to exchange files with the icom Data Suite that are to be stored or executed in the icom Data Suite. Each update packet contains a manifest in form of a file; the entries in this file describe the data contained. The manifest and the files as uncompressed tar archive together form an update packet. The files can be profile or configuration files.
Already packed packets (those already contain a MANIFEST) can already be used for an update. If several update packets are to be combined in one packet, for example a profile packet and an ASCII configuration packet (as in below example), the individual packets must be unpacked first and then the contained files must be bundled together with the manifest to a combined update packet.
The manifest is a text file (ASCII or UTF-8 without BOM) with the file name "MANIFEST" (without file name extension, e.g. .txt). It contains sections that describe the files in the archive. Empty lines are ignored. Capitalization is not ignored. Each line must start with a keyword which is followed by the "=” character and the value. No blanks are permitted directly before and after the "=". A new section starts with the keyword "FILENAME". The manifest should always be the first file that is contained in the archive. Thus, an update packet does not have to be transmitted completely to be able to see what this archive contains. Keywords contained in the manifest are:
Possible entries for FILETYPE are:
Example of a manifest for a profile packet
Example of a manifest for an ASCII configuration packet
Example of a manifest for a packet with a profile and an ASCII configuration