Re: Option to execute a command?
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Thread-index: AQHL7kJU1BT4POw5L0OnxLhGDUmecpRFVkuAgACuEoCAAAIlgIAAC5aAgAACpgCAAAnaAIAAxIAA Thread-topic: Option to execute a command? 30 mar 2011 kl. 21:11 skrev Karl Kuehn:
One thing that is missing in this conversation is that you could be running this installer targeted at a volume other than the boot volume. It is really simple to catch this case, so we should always be pushing people to do this when they write installer scripts.
Good catch, and you're probably right about -w too. My reasoning was that if an upgrade fails, you don't want a half-broken install to launch until you have a successful install (which loads -w). So to summarize, the scripts should look like so: preinstall:
#!/bin/bash
LAUNCHD=/Library/LaunchDaemons/edu.caltech.autonomy.foo.plist if [ -e "$LAUNCHD" && "$3" == "/" ]; then launchctl unload "$LAUNCHD" fi
postinstall:
#!/bin/bash
if [ "$3" == "/" ]; then launchctl load /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist fi
-- Per Olofsson System Administrator, ITS, University of Gothenburg _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com
participants (1)
-
Per Olofsson