site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com -Dan On Jan 14, 2009, at 2:39 PM, Rusty Myers wrote: On Jan 14, 2009, at 3:28 PM, Dan Wilson wrote: Thanks, Dan _______________________________________________ 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... I don't think installing both and cleaning up unwanted files will solve my problem. Both versions install the same files, just different versions. Also, I can't even get a functional metapackage with two component packages that have the same package identifier (com.company.pkg.product). Having the same identifier in both seems important for upgrade scenarios. I'm trying to build a metapackage that installs version A of a component on Tiger, and version B of the same component on Leopard. After setting the OS version requirements on each component, everything seems to work properly, but PackageMaker seems to require that each package has a different package identifier, even if the package version is different. If I manually edit the identifiers to be the same, opening the metapackage causes Installer to return an error ("Operation could not be completed. com.apple.installer.pagecontroller error -1"). Is there a way to accomplish what I'm trying to do? After a successful install, the package receipt has the package identifier shown in PackageMaker, which I expect will cause problems with upgrades. PackageMaker 3.0.1 How about install both and remove the one that isn't needed? Use a postflight script that determines OS version and deletes appropriate files?

From Bombich set-names.sh script: defaults read "$1"/System/Library/CoreServices/SystemVersion ProductVersion | awk -F. '{print $2}' Prints middle number in 10.5.6 OS version. For example, 10.5.6 would print 5. 10.4.11 would print 4. Rusty

This email sent to site_archiver@lists.apple.com