site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Thanks! -- Andy _______________________________________________ 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've been updating some of my packages to the new PackageMaker 2.0.1 under Tiger, but I'm finding that while these work fine in Tiger, if I try to install an update of an existing package that had been previously installed in Panther, the new package fails, saying that ".A newer version of the package is already installed." Looking at the receipt of the original install (done under Panther with a package created with PackageMaker 1.2), I discovered that its Info.plist contains the two keys IFMajorVersion and IFMinorVersion, both set to 0. The new plist from PackageMaker 2.0.1 doesn't create these two keys. I believe this is what's causing the problem because if I either remove these two keys from the receipt package or add them to the new package, the install works under Panther. It would seem that the Installer that runs under Panther looks at these values and if they're missing, gets confused. I'm wondering if anyone else has encountered this problem and what sort workaround there might be (other than manually adding these two keys each time I build the package under Tiger). Is the new PackageMaker supposed to create packages that are backwards compatible to the Installer that runs under Panther? This email sent to site_archiver@lists.apple.com