---

Introduction to PackageMaker User Guide

Contents:

Organization of This Document
See Also

Software packaging is the process used to put a software product into an installation package so that it can be installed by the users of the product on their computers. To package a product you use the PackageMaker application, which is part of the Xcode developer software suite.

This document shows how to use PackageMaker to create installation packages.

People who take finished product files and create installation packages for them are known as packagers. With PackageMaker, packagers accomplish these objectives:

• Enclose a software product in a transport-agnostic container for delivery to users

• Define the user install experience

• Specify how product files are placed on the user’s file system

You should read this document if you have a software product that you want to deliver to its users in a way that allows you to define certain aspects of the user install experience and details about how the product files are to be placed on the user’s file system.

To get the most out of this document, you should be familiar with Software Delivery Guide, which describes the software delivery model used in Mac OS X.

Organization of This Document

This document contains the following chapters:

• “Packaging Overview.” Describes briefly the packaging process in the context of the Mac OS X software delivery model.

• “Packaging Workflow.” Explains the workflow you should follow when creating installation packages.

This document also contains a glossary and a revision history.

See Also

• Software Delivery Guide. Explains how to deliver and install software using the PackageMaker and Installer applications. Provides a larger picture of the Mac OS X software-delivery model and more detailed information about the installation process.

• File System Overview. Conceptual information and guidelines describing the structure and usage of the Mac OS X file system. Contains information about the Mac OS X file system domains and the recommended locations for software components according to their type.

---