On 08/12/2013 05:08 PM, Stephane Sudre wrote: On Mon, Aug 12, 2013 at 3:14 PM, Matthias Schroeder <Matthias.Schroder@cern.ch> wrote: Dear all, I am building a package into which I want to integrate an existing mpkg which I want to touch as little as possible. So I decided I will run a pre-install script that will check whether the installation of the mpkg is needed at all, and if it is the script will call /usr/sbin/installer with the mpkg as argument.. The checks and the installation appear to work as expected, but there is a little complication: The installation of this mpkg requires a restart. But I want to avoid having to restart in the case that the installation of the mpkg was not required. Is there a way that the pre-install script can change the "Post-installation Behaviour" of a package of a distribution? I don't want to mark the install as failed, since I might want to install further packages even if the installation of the mpkg is not needed. Thanks in advance for your help, 1. Set your package to require a restart. 2. Don't check whether the installation of the mpkg is needed in the pre-install script. 3. Check whether the installation of the mpkg is needed in the choice requirement and disable the installation of the package if the requirement is not met. Thanks a lot, Matthias _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/matthias.schroder%40ce... This email sent to matthias.schroder@cern.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com Sounds good. I have to admit I don't recall why I decided to do the checking in the pre-install - I believe it was purely because that way it was easier to test...I will see.