|
|
The request script solicits interaction during installation and is the only place where your package can interact directly with the installer. It can be used, for example, to ask the installer if optional pieces of a package should be installed.
The output of a request script must be a list of parameters and their values. This list can include any of the parameters you created in the pkginfo(F) file (not including the 21 standard parameters) and the CLASSES parameter. The list can also introduce parameters that have not been defined elsewhere.
When your request script assigns values to a parameter, it must then make those values available to the installation environment for use by pkgadd(ADM) and also by other packaging scripts. The following example shows a request script segment that performs this task for the four parameters CLASSES, NCMPBIN, EMACS, and NCMPMAN:
# make parameters available to installation service # and any other packaging script we might have cat >$1 <<! CLASSES='$CLASSES' NCMPBIN='$NCMPBIN' EMACS='$EMACS' NCMPMAN='$NCMPMAN' !