This section describes general attributes, Oracle Solaris action attributes, and Oracle Solaris attribute tags.
The following attributes are not necessary for correct package installation, but having a shared convention reduces confusion between publishers and users.
ID of a Common Vulnerability and Exposure (CVE) that has been fixed in this Oracle Solaris release. See Critical Patch Update Packages in Updating Systems and Adding Software in Oracle Solaris 11.4 for details about how to use these values, such as how to find the oldest package where the problem was fixed.
List of additional terms that should cause this package to be returned by a search.
Human readable string that describes the entity that provides the package. This string should be the name, or name and email of an individual, or the name of an organization.
URL associated with the entity that provides the package.
Human readable string that describes the entity that creates the software. This string should be the name, or name and email of an individual, or the name of an organization.
URL associated with the entity that creates the software delivered in the package.
URL to the source code bundle for the package, if appropriate.
URL to the source code repository for the package, if appropriate.
Changeset ID for the version of the source code contained in info.repository-url.
One or more case identifiers (for example, PSARC/2008/190) associated with the ARC case (Architecture Review Committee) or cases associated with the component delivered by the package.
One or more FMRIs that represent SMF services delivered by this package. These attributes are automatically generated by pkgdepend for packages that contain SMF service manifests. See the pkgdepend(1) man page.
To provide additional metadata for a package, use an organization-specific prefix on the attribute name. Organizations can use this method to provide additional metadata for packages developed in that organization or to amend the metadata of an existing package. To amend the metadata of an existing package, you must have control over the repository where the package is published. For example, a service organization might introduce an attribute named service.example.com,support-level or com.example.service,support-level to describe a level of support for a package and its contents.
Specifies which actions in a package can be installed in a non-global zone, in the global zone, or in either a non-global or the global zone. See Handling Non-Global Zones for more information.
Oracle Solaris reverts configuration and other state by using revert tags during various administrative actions. Tag names that have the system: prefix are reserved for use by Oracle Solaris. The system:clone and system:dev-init revert tags can also be used to package third party software. Third party software cannot be packaged with any other revert tag that begins with system:.
Clears configuration and state that should not be propagated during system or zone cloning. The system:clone tag is used during clone archive creation. For example, the /etc/svc/profile/node and /etc/svc/profile/sysconfig directories are packaged with revert-tag=system:clone=* because those directories contain configuration that is specific to that system and should not be included in a clone archive.
Clears device configuration that is unique to a specific system. The system:dev-init tag is used during clone archive creation and during recovery archive creation.
See the archiveadm(8) man page for more information about the use of the system:clone and system:dev-init revert tags.
Removes unpackaged content from the /etc/svc/profile/ directories when the sysconfig unconfigure --remove-profiles command is used. See the sysconfig(8) man page for more information.