Software Distributor Administration Guide (March 2009)

Table Of Contents
The control scripts you write may be executed several times (for example, configure,
then unconfigure, then configure...) so they must be able to support multiple
executions.
You may have to re-execute or debug control scripts, especially when they generate
error or warning conditions, so your scripts should be well-written and commented.
Control script stdout and stderr are both logged, so you should restrict output
to only the information the user requires.
Make sure you specify the path to a shell that is proper for your system. If you get
the following message when you execute a script:
Cannot execute /var/adm/sw/products/PRODUCT/FILESET/
configure. Bad file number (9).
it means the shell in your script has a path that is not correct for your system.
(HP-UX 9.X scripts = #!/bin/sh and HP-UX 10.X and 11.X scripts = #!/sbin/
sh.)
11.3 Packaging Control Scripts
The following table describes the control script keywords for use in a PSF.
Table 11-2 Control Script Keywords
ExampleSize in
Bytes
TypeKeyword
/mfg/sd/scripts/checkinstall
1024
path_stringcheckinstall
/mfg/sd/scripts/preinstall
1024
path_stringpreinstall
/mfg/sd/scripts/postinstall
1024
path_stringpostinstall
/mfg/sd/scripts/unpreinstall
1024
path_stringunpreinstall
/mfg/sd/scripts/unpostinstall
1024
path_stringunpostinstall
/mfg/sd/scripts/configure
1024
path_stringconfigure
/mfg/sd/scripts/unconfigure
1024
path_stringunconfigure
/mfg/sd/scripts/verify
1024
path_stringverify
/mfg/sd/scripts/checkremove
1024
path_stringcheckremove
/mfg/sd/scripts/preremove
1024
path_stringpreremove
/mfg/sd/scripts/postremove
1024
path_stringpostremove
/mfg/sd/scripts/request
1024
path_stringrequest
/mfg/sd/scripts/subscripts
1024
path_stringcontrol_file
11.3 Packaging Control Scripts 271