site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Think again. <installTo relocatable="true"> Seeking help... 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... We are trying to ship our software and are encountering several extremely frustrating bugs with PackageMaker 3.0.1 that may be a show- stopper for us to continue developing on Leopard. On 10.4 we built our packages with a script passing various flags to packagemaker and that worked great. Now we have upgraded to 10.5.1 and we noticed that our app wasn't being installed into the /Applications folder like it should. Looking at the installer log output, we noticed the "Diverting" mumbo jumbo that was installing the new app not to /Applications, but to /Users/ justin/Projects/MyApp-1.6.0/Builds/XCode/Debug etc. Basically, some seemingly random other copy of MyApp.app on my machine (of which there are probably many development copies). Searching around, we noted some posts on this mailing list that recommended building the package from a pmdoc seemed to fix this "diverting" problem, so I worked up a pmdoc that turns off the "relocatable" flag. Click "Build and Go" in PackageMaker and it seems to be doing what I want it to do. Great. Problem solved, right? 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. So basically, what I'm left with, is instead of having a fully shell scriptable package build as we enjoyed in 10.4, is having to manually open up the .pmdoc document in PackageMaker, select the application choice's component, uncheck the "Allow relocation" checkbox (and don't bother saving because it doesn't persist), and build it from the GUI. Surely there is some workaround for this? I mean, we're even building our Windows installers from the command line on OS X nowadays... and I'm not sure how to accurately describe the sense of irony surrounding this situation to my manager. Additionally, the file permissions recommendations don't seem to "stick" when you save the .pmdoc in PackageMaker. Is this or is this not an important aspect of the package? Or is this another thing I must remember to do manually when I open my pmdoc in PackageMaker and want to build my installer? This email sent to site_archiver@lists.apple.com