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 |
1. IPS Design Goals, Concepts, and Terminology
2. Packaging Software With IPS
3. Installing, Removing, and Updating Software Packages
4. Specifying Package Dependencies
6. Modifying Package Manifests Programmatically
7. Automating System Change as Part of Package Installation
Delivering a Service that Runs Once
Supporting Package Self-Assembly in SMF Methods
Testing Whether a Configuration File Recompile Is Necessary
Limiting the Time To Wait for Self-Assembly To Complete
8. Advanced Topics For Package Updating
First determine which actions should cause a change to the system when they are installed, updated, or removed. For example, some system changes are needed to implement the software self-assembly concept described in Software Self-Assembly.
For each of those package actions, determine which existing SMF service provides the necessary system change. Alternatively, write a new service that provides the needed functionality and ensure that service is delivered to the system as described in Delivering an SMF Service.
When you have determined the set of actions that should cause a change to the system when they are installed, tag those actions in the package manifest to cause that system change to occur. The value of a tag that causes system change to occur is called an actuator.
The following actuator tags can be added to any action in a manifest:
This actuator takes the value true or false. This actuator declares that update or removal of the tagged action must be performed in a new boot environment if the package system is operating on a live image. Creation of a new boot environment is controlled by the be-policy image property. See the “Image Properties” section in the pkg(1) man page for more information about the be-policy property.
These actuators are related to SMF services.
SMF actuators take a single service FMRI as a value, possibly including globbing characters to match multiple FMRIs. If the same service FMRI is tagged by multiple actions, possibly across multiple packages being operated on, IPS only triggers that actuator once.
The following list of SMF actuators describes the effect on the service FMRI that is the value of each named actuator:
Disable the specified service prior to performing the package operation.
Refresh the specified service after completing the package operation.
Restart the specified service after completing the package operation.
Temporarily suspend the specified service prior to performing the package operation, and enable the service after completing the package operation.