Application Packaging Developer's Guide

Case Study Files

The pkginfo File

NAME=KrAzY Applications
VERSION=Version 1
CLASSES=none cfgdata admin

The prototype File

i pkginfo
i request
i i.admin
i r.cfgdata
d none bin 555 root sys
f none bin/process1 555 root other
f none bin/process2 555 root other
f none bin/process3 555 root other
f admin bin/config 500 root sys
d admin cfg 555 root sys
f admin cfg/datafile1 444 root sys
f admin cfg/datafile2 444 root sys
f admin cfg/datafile3 444 root sys
f admin cfg/datafile4 444 root sys
d cfgdata data 555 root sys

The space File

# extra space required by config data which is
# dynamically loaded onto the system
data 500 1

The i.admin Class Action Script

# PKGINST parameter provided by installation service
# BASEDIR parameter provided by installation service
while read src dest
   cp $src $dest || exit 2
# if this is the last time this script will be executed
# during the installation, do additional processing here.
if [ "$1" = ENDOFCLASS ]
# our config process will create a data file based on any changes
# made by installing files in this class; make sure the data file
# is in class `cfgdata' so special rules can apply to it during
# package removal.
   installf -c cfgdata $PKGINST $BASEDIR/data/ f 444 root
   sys || exit 2
   $BASEDIR/bin/config > $BASEDIR/data/ || exit 2
   installf -f -c cfgdata $PKGINST || exit 2
exit 0

This illustrates a rare instance in which installf is appropriate in a class action script. Because a space file has been used to reserve room on a specific file system, this new file may be safely added even though it is not included in the pkgmap file.

The r.cfgdata Removal Script

# the product manager for this package has suggested that
# the configuration data is so valuable that it should be
# backed up to $PKGSAV before it is removed!
while read path
# path names appear in reverse lexical order.
   mv $path $PKGSAV || exit 2
   rm -f $path || exit 2
exit 0