JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Packaging and Delivering Software With the Image Packaging System in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  IPS Design Goals, Concepts, and Terminology

2.  Packaging Software With IPS

3.  Installing, Removing, and Updating Software Packages

4.  Specifying Package Dependencies

5.  Allowing Variations

6.  Modifying Package Manifests Programmatically

7.  Automating System Change as Part of Package Installation

8.  Advanced Topics For Package Updating

9.  Signing IPS Packages

10.  Handling Non-Global Zones

11.  Modifying Published Packages

A.  Classifying Packages

B.  How IPS Is Used To Package the Oracle Solaris OS

Oracle Solaris Package Versioning

Oracle Solaris Incorporation Packages

Relaxing Dependency Constraints

Oracle Solaris Group Packages

Attributes and Tags

Informational Attributes

Oracle Solaris Attributes

Organization-Specific Attributes

Oracle Solaris Tags

Oracle Solaris Package Versioning

Package Identifier: FMRI described the pkg.fmri attribute and the different components of the version field, including how the version field can be used to support different models of software development. This section explains how the Oracle Solaris OS uses the version field, and provides insight into the reasons that a fine-grained versioning scheme can be useful. In your packages, you do not need to follow the same versioning scheme that the Oracle Solaris OS uses.

The meaning of each part of the version string in the following sample package FMRI is given below:


Component version. For packages that are part of the Oracle Solaris OS, this is the OS major.minor version. For other packages, this is the upstream version. For example, the component version of the following Apache Web Server package is 2.2.22:


Build version. This is used to define the OS release that this package was built for. The build version should always be 5.11 for packages created for Oracle Solaris 11.

Branch version. Oracle Solaris packages show the following information in the branch version portion of the version string of a package FMRI:


Major release number. The major or marketing development release build number. In this example, 0.175 indicates Oracle Solaris 11.


Update release number. 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.


SRU number. 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.


Reserved. This field is not currently used for Oracle Solaris packages.


SRU build number. The build number of the SRU, or the respin number for the major release.


Nightly build number. The build number for the individual nightly builds.


Time stamp. The time stamp was defined when the package was published.