What are the pro and cons of using PackageMaker as my installing solution? If you're distributing a solution that needs to put a driver in /SystemLlibrary/Extensions, an application in /Applications, a framework in /Library/Frameworks, then you seriously need an installer.

You can also use the background image of the Disk Image to provide instructions to the user. For the other 99.99%, just distribute your application inside a Disk Image and inform the user in the Read Me file he/she just needs to move the file into the Applications folder to install it. The 0.01% left is made of unusual cases like for instance if you want your application to be installed in the Applications folder of the root home directory (but this is just an example). You don't need to use an installer in 99.99% of cases. ' Do I need an installer to install my applications or documents?'įor instance, if you're distributing an application without any other files to install (Frameworks, StartupItems, Drivers, etc.), The first question you must ask yourself is: Packages are the solution used by Apple to install Mac OS X and to provide System or Applications upgrades via the Software Update solution. To install a package, all you have to do is to double-click on its icon in the Finder and the Installer.app application will be launched and will guide your through the necessary steps of the installation. It can also includes Read Me, License documents and scripts to run before or after the installation. pkg extension) which contains an archive of files to install and information on where to install them. Instead, PackageMaker is creating a package:Ī package is a bundle (with a. PackageMaker is the installing solution provided by Apple with its developer tools.Ĭontrary to other installers' solution, PackageMaker does not create self-running installer (i.e. All the pieces of information in this document still apply when you select the target to be Mac OS X 10.3 in PackageMaker. PackageMaker is available in version 3.0.4 at the time of the writing of this note. This document was written with PackageMaker 1.x in mind.

This document is targeted towards Mac OS X Developers with a minimum background on Mac OS X and notions like file paths, bundles, Developer tools.

Java for mac os x 10.2