site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Thanks for any insights, Rick _______________________________________________ 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 recently created an installer package with the PackageMaker tool under Leopard. I encountered quite a few problems, in a process that used to be fairly easy. One of the strange effects I found was related to selection of the "allow relocation" box under the Components tab for a package. If this is selected, it seems that the Installer searchers all over the hard drive for versions of the app, and may well put the installed version in an unexpected location. On a development system with versions of our app placed in various places for training and testing, this made it seem as if the installation failed to create the intended app bundle. In fact what happened was that the updated app was being put in some obscure location overtop of an old version that had been used in testing - rather than in the default /Applications folder. Our actual application can in fact be relocated, but this installer behavior makes checking that box kind of risky. Unless someone indicates I'm missing something, I'll file a bug suggesting that the detection of multiple copies of an app get reported to the user, and that the destination actually used for an installation also be indicated. The search behavior is mentioned in the PM doc, but there should be a warning as well. So my question: when would it actually be a good idea to check this box? This email sent to site_archiver@lists.apple.com