Each package is represented by a Fault Management Resource Identifier (FMRI). The full FMRI for a package consists of the scheme, a publisher, the package name, and a version string in the following format:
scheme://publisher/name@version:dateTtimeZ
The scheme, publisher, and version string are optional. In IPS command operands, you can use the smallest portion of the package name that uniquely identifies the package, and you can use the ? and * characters as glob(3C)-style wildcards to match one or more packages.
The following example package FMRI is for the suri storage library:
pkg://solaris/system/library/storage/[email protected],5.11-0.175.2.0.0.34.0:20140303T145535Z
pkg
solaris
If the publisher is specified, then the publisher name must be preceded by pkg:// or //.
system/library/storage/suri
Package names are hierarchical with an arbitrary number of components separated by forward slash (/) characters. In IPS commands, leading components of package names can be omitted if the package name that is used in the command uniquely identifies the package. If you specify the full package name but omit the publisher, the full package name can be preceded by pkg:/ or / but not by pkg:// or //. If you specify an abbreviated package name, do not use any other characters to the left of the package name.
The package version has four parts:
For components tightly bound to the operating system, the component version usually includes the value of uname -r for that version of the operating system. For a component with its own development lifecycle, the component version is a dotted release number, such as 2.4.10.
The build version must follow a comma (,). The build version specifies the version of the operating system on which the contents of the package were built.
The branch version must follow a hyphen (-). The branch version provides vendor-specific information.
Oracle Solaris packages show the following information in the branch version portion of the version string of a package FMRI:
The major or marketing development release build number. In this example, 0.175 indicates Oracle Solaris 11.
The update release number for this Oracle Solaris release. The update value is 0 for the first customer shipment of an Oracle Solaris release, 1 for the first update of that release, 2 for the second update of that release, and so forth. In this example, 1 indicates Oracle Solaris 11.1.
The Support Repository Update (SRU) number for this update release. SRUs include only bug fixes; they do not include new features. The Oracle Support Repository is available only to systems under a support contract.
This field is not currently used for Oracle Solaris packages.
The build number of the SRU, or the respin number for the major release.
The build number for the individual nightly builds.
The time stamp must follow a colon (:). The time stamp is the time the package was published in ISO-8601 basic format: YYYYMMDDTHHMMSSZ.