site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On mercredi, décembre 7, 2005, at 10:32 PM, Rich Kubota wrote: _______________________________________________ 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... A full analysis of this problem has not been made, but there's a little known feature with the installer that might be useful in this situation. This solution may not work for everyone, specifically those whose products are constrained to fitting the installation on a space limited media - like CDs. If an InstallationCheck script returns the result (1 << 6), the package will not be installed. By itself, this is no different from any other non-zero result, however, if that package is part of a meta-package installation, then only the specific package is not installed, but the remainder of the installation proceeds. This means that one could design a meta-package installer where there are 2 packages - one with the universal binary version of the bundle, kext, application, etc. and a second with the PPC version only. Each package would have their own InstallationCheck script. The InstallationCheck script for the UB version of the product would check the OS version and return (1 << 6) if OS X 10.2.x or earlier is present. The InstallationCheck script for the PPC-only package would return (1 << 6) if OS X 10.3.x or greater is present. Nice idea. I was thinking about a more radical solution. Deleting the new receipt during the postflight script if this is possible. This email sent to site_archiver@lists.apple.com