Introduction to the use of the application installation package authoring tool packages in MAC OS platform

First, Introduction

There are many packaging tools to choose from when developing applications under Windows, such as Inno Setup, InstallShield, NSIS, Advanced Installer, Qt Installer framework, etc. Even many people choose to combine Winrar+bat to create an application installation package. Mac OSX seems to have few tools to choose from, and most powerful tools need to be purchased. DMG is a compressed image file format on Mac OS X that resembles a common ISO file on Windows and can be used as a packaging tool. It is a good way to distribute the application by allowing the user to load the image directly. Many developers do the same thing:

In addition, Pkg is another common installation package format under the Mac OS x platform. Installation package program similar to the Windows platform. PKG packages typically have a series of installation processes that guide the user through the installation process. The PKG installation tool has Xcode's own package Maker (the new version of Xcode doesn't seem to be included), Packages. This blog mainly talk about the use of packages process. Packages is an open-source installation package authoring tool that can specify the file installation path, custom installation process, resource internationalization, plug-in mechanism, and execution of installation scripts to meet most of the installation scenarios.

Second, use

Packages has two modes: one is called distribution, and the installation package in this mode can contain multiple components, specify the installation location separately, and the raw packages are available for use with only one installation component is a simplified form of distribution. The meaning of the "component (Package)" in packages is explained here. In fact, in many of the installation package production software, there are "components" concept. A component (package) is a section with specific installation properties and is a logical division of the program that needs to be installed. For example, an installation package contains two parts, part of which needs to be installed into the system directory, and a part installed in the user directory. Logically it can be divided into two components (packages) that specify different installation properties for each.

To select a directory for the packages project, note that it is a good idea to select project directory as the directory where the installation files are located. Otherwise, the installation package fails to run easily. Of course, "Project Name" can be decided at will.

When the new project is completed, it will go to the project homepage, the default is to see the Settings page, you can set the installation package name (also compiled pkg file name), the installation package output location, installation package format and other information.

Standard installation procedures are divided into: Introduction, Read Me (optional), License (optional), Destination Select, installation Type, installation, summary seven steps. The plus sign on the right is the ability to customize text information for each step. Each of the main messages added is preceded by a flag flag, which is an internationalized option. The installation package produced by packages will automatically display the corresponding internationalized resources for the system language.

This is the final step in the process of customizing the installation step.

Start the Custom installation component (package). After you create a new project, you have a default component (package) with the same name as the project, which sets the organization identifier, version number, execution action, and installation options. The most important of these is the payload page.

The payload page is used to specify the installation files. Contents will show all the installation location of the system, select/library/quicklook as the installation path as follows.

When you select a folder, click the plus sign below to add the files you need to install, as an example, add a PDF file. The default installation directory is the root directory, where after we have added the files, click the Set button in settings to reset. In this way, a crosshair icon appears on the Quicklook folder icon, indicating that the file will be installed in this location.

Several new components (packages) are created as examples.

For some applications, you may need to do some extra work on the installation, where you can specify the execution script. Divided into pre-installation and post-installation execution.

、

After you add several components (packages), you can specify the package name and description for each one that will be displayed to the user at the time of installation!

After the installation package is compiled, you can start running tests:

The contents of Read me and license can be written in a txt text and specified in the installation step settings.

Specifies the installation location, not the component installation location, but the physical disk to which to install.

Ha, the installation process is finished successfully! To the specified installation location, the proper installation files appear!

Third, summary

In general, packages is a very useful tool. Its functions can meet most of the installation scene, simple operation and simple interface. In addition, packages supports plugins Oh, through the installer plugins template in Xcode, you can create a variety of plugins to enhance packages functionality and customize the installation process. As a part of the open source community, it is a conscientious act!

Http://www.cnblogs.com/csuftzzk/p/mac_os_x_make_application_installer.html

Http://files.cnblogs.com/files/findumars/Packages.zip

Introduction to the use of the application installation package authoring tool packages in MAC OS platform