Document Information
Preface
1. Designing a Package
2. Building a Package
3. Enhancing the Functionality of a Package (Tasks)
4. Verifying and Transferring a Package
5. Case Studies of Package Creation
6. Advanced Techniques for Creating Packages
Glossary
|
IndexA
B
- base directory
- The path Field
- Specifying the Base Directory
- in the administrative defaults file, The Administrative Defaults File
- using parametric path names, Using Parametric Base Directories
- using the BASEDIR parameter, Using the BASEDIR Parameter
- walking the
- Managing the Base Directory
- Walking Base Directories
- example
- Example—Analysis Scripts That Walk a BASEDIR
- Example—A request Script That Walks a Relative Parametric Path
- build class, The Special System Classes
- in a case study, The prototype File
- script, The Special System Classes
- in a case study, The Build File
- build time, Package Environment Variables
- build variable, description, Package Environment Variables
- building a package, the process, The Process of Building a Package (Task Map)
- bundled packages, Beyond Tradition
C
- certificates
- importing into package keystore, How to Import the Certificates Into the Package Keystore
- managing, Certificate Management
- trusted
- Certificate Management
- Adding Trusted Certificates to the Package Keystore
- Deleting Trusted Certificates and Private Keys From the Package Keystore
- user, Adding a User Certificate and Private Key to the Package Keystore
- checking package installation, Verifying the Integrity of a Package
- the process, Verifying and Transferring a Package (Task Map)
- checkinstall script
- Package Installation Scripts
- Script Processing During Package Installation
- Becoming Comfortable With Uncertainty
- and environment variables, Package Environment Variables Available to Scripts
- BASEDIR parameter
- Managing the Base Directory
- Using the BASEDIR Parameter
- creating installation scripts, Creating Installation Scripts
- dependency checking, Defining Package Dependencies
- design rules, Design Rules for checkinstall Scripts
- example of, Example—Analysis Scripts That Walk a BASEDIR
- how to write a, How to Gather File System Data
- patching packages, The checkinstall Script
- writing a, Gathering File System Data With the checkinstall Script
- class action script
- Package Installation Scripts
- Script Processing During Package Removal
- The Class Action Script
- behaviors, Class Action Script Behaviors
- creating installation scripts, Creating Installation Scripts
- design rules, Design Rules for Class Action Scripts
- example of, The Class Action Script
- how to write a, How to Write Class Action Scripts
- in a case study, The i.admin Class Action Script
- naming conventions, The Class Action Script
- classes, See object classes
- collectively relocatable object
- The path Field
- The path Field
- composite package
- example
- Example—Modifying a File
- Example—Creating a New File
- Example—A Composite Package
- rules for constructing, Another Look at Composite Packages
- traditional example, Example-A Traditional Solution
- composite, Composite Packages
- compver file, Package Information Files
- description, Defining Package Dependencies
- example, How to Define Package Dependencies
- how to write, How to Define Package Dependencies
- in a case study, The compver File
- control files
- description
- See also information files and installation scripts
- copyright file, Package Information Files
- example, How to Write a Copyright Message
- how to write, How to Write a Copyright Message
- in a case study
- The copyright File
- The copyright File
- writing a, Writing a Copyright Message
D
E
F
I
- i.cron installation class action script, in a case study, The i.cron Installation Class Action Script
- i.inittab installation class action script, in a case study, The i.inittab Installation Class Action Script
- Image Packaging System, Image Packaging System (IPS) Packages
- incompatible package, Defining Package Dependencies
- individually relocatable object
- The path Field
- The path Field
- install time, Package Environment Variables
- install variable, description, Package Environment Variables
- installation environment variables, Package Environment Variables Available to Scripts
- to determine Solaris version, Package Environment Variables Available to Scripts
- installation scripts
- and environment variables, Package Environment Variables Available to Scripts
- characteristics, Package Installation Scripts
- creating, Creating Installation Scripts
- exit codes, Exit Codes for Scripts
- obtaining package information, Obtaining Package Information for a Script
- processing of, Script Processing During Package Installation
- requirements for, Creating Installation Scripts
- types of
- Package Installation Scripts
- Creating Installation Scripts
- installation software database, The Installation Software Database
- installf command
- Design Rules for Procedure Scripts
- How Classes Are Processed During Package Removal
- in a case study
- The i.admin Class Action Script
- The postinstall Script
- installing classes, How Classes Are Processed During Package Installation
- installing packages on a standalone or server, example, Example – Installing to a Server or Standalone System
- installing packages to clients, example, Example – Installing to a Client System
- IPS packages, Image Packaging System (IPS) Packages
|