Creating an Icon for Your Application

If you want to provide an icon for your application, you can use iconedit(1) to create one. See the iconedit(1) man page for more information. Before you save the icon, be sure your iconedit settings are as follows:

• Black and White (not color)
• Format is XView Icon
• Size is 64

You set Size and Format using the Properties menu.

You must also specify the location of the icon in the pkginfo file. Set the SUNW_ICON parameter to the path name of the icon. The path name should be the relative path to the icon.

Using Clusters

A cluster is a group of one or more software objects such that each object is either a software package or another cluster.

Clusters provide a modular view of the contents of the installation medium. By using the admintool add software capability, a user can display a list of the clusters contained in a product. The user can then choose which clusters to install.

Clusters can also simplify the removal and upgrade of software packages and the distribution of localization modules and machine-dependent code. You can package each localization module separately, allowing the user to install only the needed modules. You can also put machine-dependent code in individual packages so that only the code for the specific system is installed.

Contents and Order Files

You can use four files to create clusters for your package:

• .cdtoc - the CD-ROM table of contents file
• .clustertoc - the cluster table of contents file
• .packagetoc - the package table of contents file
• .order - the package installation order file

These files are optional. You need to use them only if you are using clusters.

Figure 4-1 shows an example of a directory hierarchy for a CD-ROM, including the locations of the contents and order files. A product can consist of multiple clusters, some of which may be optional.

Figure 4-1

If your package has other locales than C (English), there would be a directory under locale for each locale. Each locale directory would contain the localized .clustertoc and .packagetoc files.

.cdtoc File

The .cdtoc resides in the top-level directory on the CD-ROM. It is a text file that describes the location of each product on a CD-ROM. This file is not required to define clusters, but your CD_ROM should contain one if you are putting multiple software products on one CD-ROM.

Each line in the file has the following form:

PARAM=value

PARAM can be one of:

• PRODNAME - full name of the product
• PRODVERS - version of the product
• PRODDIR - the directory containing the product

The parameters are grouped by product and PRODNAME should be the first parameter for each product. See the cdtoc(4) man page for detailed information.

.clustertoc File

The .clustertoc file describes all the clusters that make up a product, listing the packages contained in each cluster. This is the only file that is required to define clusters for a product.

The .clustertoc file must be in the locale directory for the product. Each product can have one .clustertoc file describing all the clusters in the product.

Each line in the file has the following format:

PARAM=value

Parameters are grouped by cluster with the first parameter for a group being CLUSTER=identifier and the last parameter for a group being END. See the clustertoc(4) man page for a complete description of the parameters.

.packagetoc File

The .packagetoc file describes the packages that make up a product. This file must also be in the appropriate subdirectory of the locale directory for the product. There can only be one .packagetoc per product.

---

Note - If your product has a .packagetoc file, it must also have a .order file.

---

Each line in the file has the following form:

PARAM=value

Parameters are grouped by package with the first parameter for a package being PKG=identifier. See the packagetoc(4) man page for a complete description of the parameters.

.order File

The .order file is a text file that specifies the order in which the packages must be installed. The file consists of a list of package identifiers, one per line. The .order file resides in the product directory (the directory specified for the product in the .cdtoc file). This file is not required to use package clusters. There can be only one .order file per product.