Attributes and Tags

This section describes general and Oracle Solaris action attributes and Oracle Solaris attribute tags.

Informational Attributes

The following attributes are not necessary for correct package installation, but having a shared convention reduces confusion between publishers and users.

info.classification

See Set Actions for information about the info.classification attribute. See a list of classifications in Appendix A, Classifying Packages.

info.keyword

A list of additional terms that should cause this package to be returned by a search.

info.maintainer

A 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.

info.maintainer-url

A URL associated with the entity that provides the package.

info.upstream

A 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.

info.upstream-url

A URL associated with the entity that creates the software delivered in the package.

info.source-url

A URL to the source code bundle for the package, if appropriate.

info.repository-url

A URL to the source code repository for the package, if appropriate.

info.repository-changeset

A changeset ID for the version of the source code contained in info.repository-url.

Oracle Solaris Attributes

org.opensolaris.arc-caseid

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.

org.opensolaris.smf.fmri

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.

Organization-Specific Attributes

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.

Oracle Solaris Tags

variant.opensolaris.zone

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 Chapter 10, Handling Non-Global Zones for more information.