site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Dec 17, 2007, at 12:04 PM, Nathan Duran wrote: On Dec 17, 2007, at 9:53 AM, Justin Greenfield wrote: <installTo relocatable="true"> Nathan, Here is the only workaround we've found: Pretty bizarre and totally frustrating. Justin _______________________________________________ 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... Save the .pmdoc. Build it from the command line. Run the package. Diverting again... Open .pmdoc back up in PackageMaker... the "relocatable" checkbox is selected again for no reason. Uncheck it. Save it. Open the .pmdoc bundle, look at the XML. No. That's not what I want. I *just* turned that off. So I edit the XML to say relocatable="false". Build it from the command line. Run the package. Diverting.... No, that's not what it should do. Same thing happens to me and no one's offered a fix or an explanation to date. The only way I was able to get rid of the problem in my own projects was to create brand new ones and change my build scripts to use the new 10.5 syntax. "Compatibility mode" flat out does not work and actually seems to damage something somewhere. We ditched the 10.4 compatibility mode and started with a blank pmdoc. All I know for sure is that the PackageMaker GUI has a lot of bugs. Using a project relative path to point to the app/component being packaged, as I was doing, breaks all kinds of things. Changing that to an absolute path lets you save things like file permissions and the "allow relocation" setting. Something about using the relative path setting completely screws up the rest of the settings. Using an absolute path at least maintains the correct settings from one session to the next. This email sent to site_archiver@lists.apple.com