| 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 |
| 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
8. Advanced Topics For Package Updating
Avoiding Conflicting Package Content
Renaming, Merging and Splitting Packages
Preserving Editable Files that Migrate
Moving Unpackaged Contents on Directory Removal or Rename
Delivering Multiple Implementations of an Application
Delivering Directories To Be Shared Across Boot Environments
How To Deliver Content to Shared Directories
Package obsoletion is the mechanism by which packages are emptied of contents and removed from the system. An obsoleted package does not satisfy require dependencies. Update fails if an installed package has a require dependency on a package that has become obsolete, unless a newer version of the installed package is available that does not contain the require dependency.
A package is made obsolete by publishing a new version with no content except for the following set action:
set name=pkg.obsolete value=true
A package can be made non-obsolete by publishing newer versions. Users who update when an installed package is obsolete lose that package. Users who updated before the package was obsolete and do not update again until after a newer version of the package is published are updated to that newer version.
|