Software Package Builder 5.0 User's Guide
NOTE: The depot properties, which are set by SD when the depot is created are not valid PSF
attributes. Therefore, the Depot Properties will appear in the PSF as comments.When a PSF is
created from a depot, the source information for files is lost.
Using Control Scripts
You can use control scripts to customize the behavior of your software package. SD-UX supports
execution of both product and fileset control scripts. These shell scripts allow you to perform
customized checks and operations as part of your regular software management tasks. The
swinstall, swconfig, swverify, swask, and swremove commands can execute one or more
of these scripts. Control scripts are usually supplied by software vendors, but you can write your
own. All control scripts are optional.
Product level control scripts are run if any fileset within that product is selected for installation,
configuration, verification, or removal. The activities in product control scripts must pertain to
all filesets in that product, but not to any one fileset in particular.
Actions you want to apply to every fileset in a product should be in the appropriate product
level control script. Fileset scripts must pertain only to the installation, configuration, or removal
of that fileset, and not to any other fileset or to a parent product.
Control scripts can perform a wide variety of customizing and configuration tasks, such as (but
not limited to):
• Verifying if someone is actively using the product and, if so, preventing reinstallation, update
or removal
• Ensuring the local host system is compatible with the software (scripts can check beyond
the compatibility enforced by the product's uname attributes)
• Removing obsolete files or previously installed versions of the product
• Creating links to, or additional copies of, files after they have been installed
• Copying configurable files into place on first-time installation
• Conditionally copying configurable files into place on later updates
• Modifying existing configuration files for new features
• Rebuilding custom versions of configuration files
• Creating device files or custom programs
• Killing and/or starting daemons
For more detailed information, refer to the chapter regarding the use of control scripts in the
Software Distributor Administration Guide located at the following Web site: http://
docs.hp.com/en/SD
Additional Information
For more information about SPB, see the SPB Help system and Quick Start Tutorial. An example
of some of the topics available in the online help include:
• Advanced Options Dialog Box
• Bundles Dialog Box
• Subproducts Dialog Box
• Vendor Defined Attributes Dialog Box
• Dependency Attributes
• Setting an OR Relationship for Dependency Attributes
44 Advanced Features