Manifest report fields
|
Note:
If you create your own manifests, use the field names listed in the
Field Name in Manifestcolumn to name your fields. |
| Field Name in Manifest | Field Name in UI | Description |
|---|---|---|
| General properties: | ||
| BASENAME | Basename |
The filename portion of the file's pathname. If this field is highlighted, the QNX Software Center found a matching file, but with a different basename. See the description of the Errors (VIOLATION) field for more information. |
| DIRECTORY | Directory | The directory in which the file resides. |
| NAME | Name | For the manifest generated by a scan, the basename of the file. For a report, the path of the file on the target or host, depending on whether the report is based on a target scan or host scan. |
| PUBLISHED_DATE | Published | Represents the publication date or the build date of the package. It is derived from various package timestamps. |
| TARGETPATH | Target Path | For a target scan, the path of the file on the target. For an installation scan, the path of the file from the root of the installation. |
| SBOM | Software bill of materials | Link to the software bill of materials. Provides a detailed list of all the components, libraries, and dependencies included in the QNX application. |
| File attributes and checksums: | ||
| ARCHITECTURE | Architecture | The processor architecture of the file. |
| BUILDID | Build ID |
An ID, encoded in hex, that uniquely identifies the binary payload of the file. This ID doesn't change even when the binary is stripped. If this field is highlighted, the QNX Software Center found a matching file, but with a different build ID. See the description of the Errors (VIOLATION) field for more information. |
| DIGESTSHA512 | Digestsha512 |
A Secure Hash Algorithm 512-bit checksum, encoded in base64, for validating the integrity of the file. If this field is highlighted, the QNX Software Center found a matching file, but with a different checksum. See the description of the Errors (VIOLATION) field for more information. |
| DIGESTSHA512HEX | Digestsha512hex |
A Secure Hash Algorithm 512-bit checksum, encoded in hex. This field contains values if you generate a target manifest with qscan.sh. If this field is highlighted, the QNX Software Center found a matching file, but with a different checksum. See the description of the Errors (VIOLATION) field for more information. |
| LINKS_TO | Links to | If a file is a symbolic link, this field lists the actual file that the link points to. |
| SIZE | Size |
The size of the file, in bytes. If this field is highlighted, the QNX Software Center found a matching file, but of a different size. See the description of the Errors (VIOLATION) field for more information. |
| TYPE | Type | The file format (for instance, QNX/Elf). |
| Parent package properties: | ||
| CATEGORY | Category |
The category of the package to which the file belongs. The QNX Software Center uses the value of this field to organize packages into logical sets. |
| PACKAGE | Package | This field combines the information in the Package Id and Package Version Internal fields. |
| PACKAGEID | Package Id | The unique alphanumeric ID of the package to which the file belongs. |
| PACKAGEINVERSION | Package Internal Version | The internal version of the package to which the file belongs. |
| PACKAGENAME | Package Name | The name of the package to which the file belongs. |
| PACKAGENAMEV | Package Full | This field combines the information in the Package Name and Package Version fields. |
| PACKAGEVERSION | Package Version | The version of the package to which the file belongs. |
| PRODUCT | Product |
The product to which the file's parent package belongs. Examples of products include QNX Software Development Platform, QNX Hypervisor, and QNX OS for Safety. |
| RELEASE | Release |
Refers to the "tag.release" property of the package (package artifact). |
| FOLDER | Release Folder |
Refers to the "server.folderName" property of the package (package artifact). |
| Compliance properties: |
Note:
To access any licensing documents mentioned below, visit the Licensing Information page on
the QNX website:
https://www.qnx.com/download/group.html?programid=29179
|
|
| CODE_PROVIDED (deprecated) | Code provided | No longer populated in the manifest. Relevant only to QNX SDP 7.0 and related products. See the QNX Software Development Platform 7.0 License Supplement for more information. |
| END_USER_LICENSE | End user license | Indicates the end-user license terms or where to find them. |
| ENGAGEMENT_MODEL (deprecated) | Engagement model | No longer populated in the manifest. Relevant only to QNX SDP 7.0 and related products. See the QNX Software Development Platform 7.0 License Supplement for more information. |
| OSS | OSS Compliance | If applicable, this field provides a link to the text of the OSS licenses. |
| REDIST | Target | Previously called Redistributable. Possible values: Target, or non-Target. If set to Target, this field indicates that the file is intended for a target image. Otherwise the file is a host tool, documentation, source code, or similar, none of which is intended to be copied to a target. |
| STATUS | Status |
The software maturity of the file (See Package status
under Deploy licenses to users). |
| SUBSYSTEM | Subsystem |
Files that are eligible to be licensed for distribution are assigned to a
runtime subsystem. This field identifies the runtime subsystem under which the
given file can be licensed for production. For more information, go to QNX Runtime Bundle License Agreement. |
| RUNCOMP | Runtime Component |
QNX runtime component that's active or in use for the specific software package (eg., QNX Hypervisor for Safety). For more information, go to QNX Runtime Bundle License Agreement. |
| TYPE_OF_SOFTWARE | Type of software | Relevant only to QNX SDP 7.0 and related products. See the QNX Software Development Platform 7.0 License Supplement for more information. |
| Errors: | ||
| VIOLATION | Errors |
Some report options compare the scanned properties of each file in a target manifest to the properties defined for that file by the myQNX server or by the current installation. If a mismatch is detected, the Errors field flags it. (See the table below for the comparisons performed by each report option.) When performing these comparisons, the QNX Software Center attempts to match files across the following properties: Basename, Architecture, Build ID, Size, and Digestsha512 checksum. If the match is inexact, the Errors field contains a weighted percentage figure to indicate how much the files match. If all of the files in a directory match, the Errors field for that directory is empty. Otherwise, the field contains a message that indicates the number and type of errors found in the top level of the directory. Note:
Hover your pointer over the Errors field to see which properties do or don't match.
Exported reports include this matched/unmatched data.
|
How file properties are compared
The following table summarizes how each report option compares file properties. (See the description of the Errors field for how property mismatches are reported.)
| Option | Comparison |
|---|---|
| Scan installation folder | Compare the scanned properties of each file to the properties defined for that file in the package data of the current installation. |
| Scan host folder | Same as Scan installation folder. |
| Import file with scan data | Compare the scanned properties of each file to the properties defined for that file on the myQNX server. If the server can't be reached, compare the scanned properties with the properties defined in the package data of the current installation. |
| -reportImportQScan | Same as Import file with scan data. |
| -fileInfo | No comparison performed. |
| -fileSearch | No comparison performed. |