StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><a href="http://s.sudre.free.fr/Stuff/PackageMaker_Howto.html" rel="noreferrer">Here</a> is a good How-to</p> <blockquote> <p>There are 7 types of scripts than can be launched during the Installation Process:</p> <p><strong>InstallationCheck:</strong> This script is launched at the beginning of the installation process (even before the Authentication step). It can be used to check that the Package can be installed on this computer.</p> <p><strong>VolumeCheck:</strong> This script is launched in the "Select Destination" step. It is used to determine on which volume the Package can be installed.</p> <p><strong>preflight:</strong> This script is launched just after the user clicked on the "Install" button.</p> <p><strong>preinstall / preupgrade:</strong> This script is launched after the preflight script if there's one (in the case of a single package installation); otherwise just after the user clicked on the "Install" button.</p> <p>As you see, there's 2 types of scripts here. The preinstall one is launched when the Package has never been installed (from an Installer.app point of view), the preupgrade one is launched when the Package has already been installed. To determine whether a Package has already been installed or not, Installer.app is having a look at the content of the following directory: /Library/Receipts. If there's a file named PackageName.pkg within it, then the Package has already been installed, otherwise it's the first install.</p> <p><strong>postinstall / postupgrade:</strong> This script is launched after the files in the package have been installed. See (preinstall / preupgrade) to see which one is launched.</p> <p><strong>postflight:</strong> This script is launched after the postinstall / postupgrade script or when the package has been installed.</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload