- When is it better to use package installation as opposed to drag-and-drop installation?
- How is a metapackage different from a package?
- What scripts can be run during installation?
- Describe the scenarios for how owner and permissions are determined on installed files and folders.
- How do you localize installation?
It’s best to use package installation when processes need to be started or stopped, or the install needs to put software in multiple locations throughout the system. Package installation is also preferred when you need to verify that certain components are already on the system or that a certain version of Mac OS X is being used.
A metapackage contains other packages and metapackages to install.
These scripts can be run during installation: preinstall, postinstall, preupgrade, postupgrade, preflight, postflight, InstallationCheck, and VolumeCheck.
If authentication is not required, all new files and folders are installed as the user that runs Installer. If authentication is required, ownership is determined by the owner of the files within the package. Permissions always follow the files within the package for new files and folders. Existing folder permissions will not be changed unless Overwrite Permissions is selected in PackageMaker.
Put the resources for each language in its own folder called languagename.proj.
Another reason to use package installation would be to automate the process of mass software installation. Installer packages allow you to have a professional-looking appearance that is customized to your particular software, is easy to use for users, and can be used to upgrade software.