site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On 2006/02/05, at 14:32, Peter Bierman wrote: -pmb _______________________________________________ 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... Thanks. The old package does not have a CFBundleID in its Info.plist, I've found deleting the CFBundleID from the new packages give us the behavior that any package will 'upgrade' any other. I think this is the best way to go, even if it is a hack. If the packages have the same name/CFBundleID, then the package with the lower version will not replace the newer one. So you can either repackage the old software into a package with a unique name/CFBundleID, or you can adjust the version numbers. I've inherited a binary that shipped last year that our customer wants to be able to install over our soon-to-be shipping new binary. It has no bundle versioning -- no version.plists anywhere in the original tree and no BundleVersions.plist. When the old binary is installed after the new on 10.4, the Install selection step has an "Install" button (even though there is still a .pkg receipt in /Library/Receipts), not an "Upgrade" button, and the install errors out with "There is nothing to install". Is there anything I can do to the new install package to make the old package just install itself as an upgrade? It's important the packages install as upgrades because we have upgrade scripts we have to run... _______________________________________________ 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/bierman% 40apple.com This email sent to bierman@apple.com This email sent to site_archiver@lists.apple.com