With IPS, you can update all of the packages on your system that have available updates. Or, you can update individual packages that are not constrained by package dependencies or image policy. If a package is constrained, a message indicating what constraint is preventing the installation or update is provided. Package constraints generally represent a dependency or a version issue.
For some package installations or updates, a clone or backup BE is automatically created. If a clone (new) BE is created, the changes are made in the clone and the current BE is not touched. To see the changes, reboot the new clone BE. If you are not satisfied with the changes, you can reboot the original BE. If a backup BE is created, the changes are made in the current BE and the backup BE becomes a clone of the current BE before the changes were made. If you are not satisfied with the changes, you can reboot the backup BE. You can specify pkg command options and image policy settings to explicitly request a new or backup BE. See Adding and Updating Software in Oracle Solaris 11.3 and the pkg(1) man page.
The following options are available:
Adding software packages after an installation – To add packages, use the pkg install command. See Chapter 3, Installing and Updating Software Packages in Adding and Updating Software in Oracle Solaris 11.3.
Adding a selected package or packages after an installation – You can update just one package or a few packages by specifying the package or packages on the command line, as shown in the following example. Note that other packages might be automatically updated or installed due to existing dependencies.
# pkg update tcsh
Updating all of the packages on your installed system – Update all of the packages on your system that have available updates as follows:
# pkg update
If you want to display information about which software packages will be installed without actually installing the packages, specify the –n and –v options with the pkg update command:
# pkg update -nv
Depending on your package repository content, your system could be updated automatically from one Oracle Solaris 11 release to a subsequent Oracle Solaris 11 release. For more information about controlling a system upgrade, see Chapter 4, Updating or Upgrading an Oracle Solaris Image in Adding and Updating Software in Oracle Solaris 11.3.
Display a list of installed packages that have available updates as follows:
# pkg list -u '*jre*'NAME (PUBLISHER) VERSION IFOruntime/java/jre-7 1.7.0.72.14 i--$pkg list -n jre-7NAME (PUBLISHER) VERSION IFOruntime/java/jre-7 1.7.0.76.13 ---$ pkg list -af jre-7NAME (PUBLISHER) VERSION IFOruntime/java/jre-7 1.7.0.76.13 ---runtime/java/jre-7 1.7.0.72.14 i--runtime/java/jre-7 1.7.0.65.17 ---runtime/java/jre-7 1.7.0.60.19 ---runtime/java/jre-7 1.7.0.55.13 ---runtime/java/jre-7 1.7.0.51.34 ---...
Install package updates that deliver fixes – Apply Support Repository Updates (SRUs) as needed. SRUs occur on a regular basis. Note that SRUs apply to the current Oracle Solaris 11 release only and are generally not provided for previous releases.