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

Avoiding Conflicting Package Content

Renaming, Merging and Splitting Packages

Renaming a Single Package

Merging Two Packages

One Package Absorbs Another

Two Packages Are Renamed

Splitting a Package

Obsoleting 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

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

Preserving Editable Files that Migrate

One common issue with updating packages is the migration of editable files, either moving between packages or changing location in the installed file system.

Migrating editable files between packages.

IPS attempts to migrate editable files that move between packages if the file name and file path have not changed. Renaming a package is an example of moving files between packages.

Migrating editable files in the file system.

If the file path changes, ensure the original_name attribute is assigned to preserve the user's customizations of the file.

If the file action in the package that originally delivered this file does not contain the attribute original_name, add that attribute in the updated package. Set the value of the attribute to the name of the originating package, followed by a colon and the original path to the file without a leading /.

Once the original_name attribute is present on an editable file, do not change the attribute value. This value acts as a unique identifier for all moves going forward so that the user's content is properly preserved regardless of the number of versions skipped on an update.