Assign the package objects in the prototype file the desired class names. For example, assigning objects to an application and manpage class would look like:
f manpage /usr/share/man/manl/myappl.1l f application /usr/bin/myappl
in the pkginfo file to contain the class names you want
to use in your package. For example, entries for the application and manpage classes would look like:
CLASSES=manpage application none
The none class is always installed first and
removed last, regardless of where it appears in the definition of the
If you are a creating class action script for a file belonging to the sed, awk, or build class, make the directory containing the package object your current working directory.
Create the class action scripts or package objects (for files belonging to the sed, awk, or build class). An installation script for a class named application would be named i.application and a removal script would be named r.application.
Remember, when a file is part of a class that has a class action script, the script must install the file. The pkgadd command does not install files for which a class action script exists, although it does verify the installation. And, if you define a class but do not deliver a class action script, the only action taken for that class is to copy components from the installation medium to the target system (the default pkgadd behavior).
Complete one of the following tasks.
If you have not created your prototype file, complete the procedure How to Create a prototype File Using the pkgproto Command, and skip to Step 7.
If you have already created your prototype file, edit it and add an entry for each installation script you just created.
Build your package.
See How to Build a Package, if needed.
After you build the package, install it to confirm that it installs correctly and verify its integrity. Chapter 4, Verifying and Transferring a Package explains how to do this and provides step-by-step instructions on how to transfer your verified package to a distribution medium.