site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=8Ue0AxZm0ynk5gkVgijx7e3aZQkOTzjs7yQYhZjhaDs=; b=XPZwZo3G+W1c1U/qWbeuSxYW+6IPF0ByirROv4InrYYJV5p6xhL9qQteoa6D8n3sDF 3A9+iB4jBh2guvzWnerMdc/r+0rizrg/kREwcU6yAmK1pvV5A1rDoUrJ2duiBsL4Mege 2MkTra+pV5394wn3wGDIBRPhouV08gBzuhFuk= On Sep 5, 2011, at 7:02 AM, Per Olofsson wrote:

...

If by the Macintosh Volume, you mean the Startup Disk, you just need to allow the package to install only on the root volume.

And note that this package will then fail to install with DeployStudio, InstaDMG, and on NetInstall NetRestore images. Whatever dependency you have should should probably be checked with a installation check script instead.

Actually, for command line installs the 'root volume only' marker is totally ignored. So InstaDMG and the others will happily install it. The problem that often occurs in cases like this is that something in the pre- or post-flight scripts assumes that / is the install location, and so gets itself in trouble. The general solution there is to make sure that pre- or post-flight scripts use the $3 input to correctly determine where things should go, and also detect that it is a command line install (the COMMAND_LINE_INSTALL environment variable) and then not do things that would be inappropriate (show dialogs, load kexts, etc). -- Karl Kuehn larkost@softhome.net _______________________________________________ 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