| Skip Navigation Links | |
| Exit Print View | |
|
Application Packaging Developer's Guide Oracle Solaris 10 1/13 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Application Packaging Developer's Guide Oracle Solaris 10 1/13 Information Library |
3. Enhancing the Functionality of a Package (Tasks)
4. Verifying and Transferring a Package
5. Case Studies of Package Creation
The Administrative Defaults File
Becoming Comfortable With Uncertainty
Using Parametric Base Directories
Examples--Using Parametric Base Directories
Example--Analysis Scripts That Walk a BASEDIR
Using Relative Parametric Paths
Example--A request Script That Walks a Relative Parametric Path
Supporting Relocation in a Heterogeneous Environment
Example-A Traditional Relocatable Package
Example-A Traditional Absolute Package
Example-A Traditional Solution
Another Look at Composite Packages
Making Absolute Path Names Look Relocatable
Making Packages Remotely Installable
Example - Installing to a Client System
Example - Installing to a Server or Standalone System
Example - Mounting Shared File Systems
Creating Class Archive Packages
Structure of the Archive Package Directory
The full capabilities of System V packaging as implemented in the Oracle Solaris OS provide a powerful tool for the installation of software products. As a package designer, you can take advantage of these capabilities. Packages that are not part of the Oracle Solaris OS (unbundled packages) may use the class mechanism to customize server/client installations. Relocatable packages can be designed to accommodate the desires of the administrator. A complex product can be delivered as a set of composite packages that automatically resolve package dependencies. Upgrading and patching may be customized by the package designer. Patched packages can be delivered in the same way as unpatched packages, and the backout archives can also be included in the product.
This is a list of the overview information in this chapter.
|