Specifications

Red Hat Enterprise Linux to Oracle Solaris Porting Guide
94
Implementation Differences for Packaging
The following table lists out the basic infrastructure-level differences for packaging on both the
platforms.
TABLE 10-1. INFRASTRUCTURE DIFFERENCES
RHEL ORACLE SOLARIS 11
RPM packages are provided as compressed archive files that
contain one or more files, as well as instructions specifying
installation information about those files, including the
ownerships and permissions that should be applied to each
file during installation.
An IPS package is made of a series of actions. Actions are
described in the manifest of a package and they are used for
defining the files and directories of the package, setting
package attributes, declaring dependencies on other
packages, creating users and groups, and installing device
drivers. Actions represent the installable objects on a system.
Every action consists primarily of its name and a key attribute.
Together, these refer to a unique object as it follows a version
history.
Package files have four-part names, which typically look
something like this:
kernel-smp-2.6.32.9-3.i686.rpm
Here, the four parts of each name are separated from each
other by dashes or periods. The structure of the package file
name is as follows:
name-version-release.architecture.rpm
Each IPS package is represented by a Fault Management
Resource Identifier (FMRI). For example, the FMRI
pkg://solaris/system/library@0.5.11,5.11-
0.151.0.1:20101105T004750Z consists of the following
sequence of information:
* Scheme: pkg
* Publisher: Oracle Solaris
* Category: system
* Package name: library
* Version string, which consists of four components :
• Component version : 5.11
• Build version: 5.11
• Branch version: 151.0.1
− Timestamp in ISO-8601 basic format:
20101105T004750Z
Package Administration and Managing Dependencies and
Upgrades
Table 10-2 shows the differences in commands and sequence of steps required to administer packages
on the two platforms.