site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com -------8<-------------8<------------8<------------8<--------- IFPkgFlagInstallFat optional data type: BOOL default value: No example: Yes -------8<-------------8<------------8<------------8<--------- I saw that this flag is not supported in PackageMaker (XCode 2.2). _______________________________________________ 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/ryanc%40apple.com _______________________________________________ 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... IFPkgFlagInstallFat is ignored in 10.4 and later due to our move to Universal binaries. We don't want developers to install thin binaries if they have a universal binary. Chris According to http://developer.apple.com/documentation/ DeveloperTools/Conceptual/SoftwareDistribution/Concepts/ sd_pkg_flags.html#//apple_ref/doc/uid/20001940: If the binary contains code for multiple platforms, should Installer install all of them? (If not, Installer strips out all but the code necessary for the current platform.) Important: If you are installing .o or .a files as part of your package, they will be thinned along with any other binaries. To prevent this outcome, set the value for this key to Yes. How does it come that when IFPkgFlagInstallFat is set to false, a Package installs both the PPC and i386 architecture of universal binaries on a PowerPC PowerMac. This email sent to ryanc@apple.com This email sent to site_archiver@lists.apple.com