Advanced Search

Log In | Not a Member?

Contact ADC

< Previous PageNext Page > Hide TOC

Creating a Metapackage

To create a metapackage, you perform the following tasks:

1. Create the metapackage project directory.

2. Create the metapackage file.

The following sections describe these tasks in detail.

In this section:

Create the Metapackage Project Directory
Create the Metapackage File

Create the Metapackage Project Directory

To facilitate the creation of an installation package, you should create a metapackage project directory to store all the files you need in the process. The metapackage project directory contains directories that hold the product’s component packages, product information files, executable-based installation requirements, and install-operation files. Listing 6-1 shows a metapackage project directory.

Listing 6-1  A metapackage project directory

LevonMeta-1.0.0/

    packages/

        Levon.pkg

        LevonDoc.pkg

        SharedServices.pkg

    product_info/

        Welcome.rtf

        ReadMe.rtf

        License.rtf

        Conclusion.rtf

    extras/

        InstallationCheck

        VolumeCheck

        preflight

        postinstall

        postupgrade

Create the Metapackage File

A metapackage project specifies the following items:

• Title: The name used to identify this metapackage to the user during installation.

• Description: This package’s description, displayed by the Installer application in the Customization pane for an enclosing metapackage when the user highlights this metapackage.

• Packages directory: The directory that contains the packages this metapackage contains.

  The directory may reside inside or outside the generated metapackage, depending on whether you want to discourage users from installing packages individually. If the directory resides inside the metapackage, you must copy the component packages from the packages directory in the metapackage project directory to the directory you designated as the package holder in the metapackage.

• Extras directory: The directory that contains executable files that specify installation requirements and install operations.

To define a metapackage-based installation process, use PackageMaker to:

1. Create a metapackage project.

2. Add product information files to the project by using Installer Interface Editor.

3. In the metapackage project directory, identify the subdirectory that contains executable files specifying installation requirements and install operations.

4. Add install choices by adding the packages in the packages subdirectory of the project directory to the metapackage project’s packages list.

   Specify the initial selection state of each choice. Choices you identify as required are selected in the Installer Custom Install pane, but the user cannot deselect them.

5. Build the metapackage.

   If you choose to place the metapackage’s packages inside the metapackage itself (mainly to discourage the individual installation of product components), copy the packages to the appropriate directory in the generated metapackage file. (You can reveal the contents of the metapackage in the Finder using the Show Package Contents command.)

< Previous PageNext Page > Hide TOC

Did this document help you? Yes: Tell us what works for you. It’s good, but: Report typos, inaccuracies, and so forth. It wasn’t helpful: Tell us what would have helped.

	Get information on Apple products. Visit the Apple Store online or at retail locations. 1-800-MY-APPLE Copyright © 2007 Apple Inc. All rights reserved. | Terms of use | Privacy Notice