site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Fri, Oct 9, 2009 at 7:22 PM, Iceberg-Dev <dev.iceberg@gmail.com> wrote:
Apple does not follow this recommendation so just don't follow it if you don't want to. Just don't overwrite permissions and you will be fine.
Yet, considering 4., I would recommend using 2 packages. one for the common components and another for the ones that need to be install only when specific requirements are met.
OK. Not splitting the package up into a component for each system directory makes it much simpler. I'm trying to decide whether to just install the agent's launchd.plist to a temporary location and handle it in a postflight script (simpler) or split up common, 10.4-specific and 10.5+ behaviors into separate sub-packages as you recommend and turn the top-level package into a metapackage. That would take OS detection out of the scripts, but I'd have to carefully plan which actions go in which of the three postflights.
If the OS target is 10.5, postinstall and preinstall are the same as postflight and preflight.
OK... it does look like the other options disappeared when PackageMaker switched to targeting 10.5. They're back after switching back to 10.4. In a 10.4-targeted package, does 10.5 still treat *install the same as *flight? By the way, I was about to ask if Iceberg could be scripted, but found freeze. Great! Unfortunately, when I run freeze on my current project, it spits out "freeze: Build failed / Insufficient privileges set". I have no problem building from the GUI. Any idea what's going on here? _______________________________________________ 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