site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Hi, we release software quarterly, and customers install new releases side-by-side with old releases. With PackageMaker 3.0 and Tiger / Leopard, we had to apply an ugly workaround to PackageMaker to strip the relocation flag from the created package, else it would overwrite previous installations. Since the workaround is scriptable, we could live with that. Now it turns out that Snow Leopard does relocate the package again, overwriting previous installations in the Trashcan and other arbitrary places. This is not what I want! Removing 'IFPkgPathMappings' from the finished package does not help anymore, neither does stripping '<mod>relocatable</mod>' nor setting 'relocatable="false"'. For Leopard, it also helped to set a unique 'Package Identifier' (we did this by adding the version number, i.e. com.company.programXXX.pkg), which does not resolve the issue for Snow Leopard. My last hope was setting a unique bundle name in the program's Info.plist, which leads to a unique 'bundle id' in distribution.dist: distribution.dist: <relocate search-id="pkmktoken2"> distribution.dist: <bundle id="com.company.programXXX"/> distribution.dist: </relocate> which did not help either. This is plain madness by now! Or am I misunderstanding something? Please, please provide some insight, or finally fix PackageMaker. Cheers, Mario Emmenlauer Hey Rick, Here's what works for me: It works perfectly! Thanks a lot! BTW: Removing IFPkgPathMappings was sufficient, IFPkgRelocatedPath does not appear in my package. Do you know if it is still needed with mpkg from PackageMaker 3.0.3? Best, Mario Emmenlauer -Rick Hi Bill, I'm referencing an old message here, where you adress my exact problem: I would very much like to get my hands on this specific email, however I could not find it in the archives (maybe it was on a different list? You post too frequent to be sure:-) ). My problem is that I generate the PackageMaker configuration auto- matically, and call PackageMaker with it. The relocatable flag is then *always* turned on, no matter what I specify in the xml. I tried PackageMaker versions 3.0.0 - 3.0.3 to no success. Can you tell me how to rip out the relocatable flag from either the xml before running PackageMaker, or from the final mpkg package? Best, Mario _______________________________________________ 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/rcc2%40cornell.edu -- Dipl. Inf. Mario Emmenlauer Cell: +49-(0)176-23463809 Bitplane AG Office: +41-(0)44-430-1106 Badenerstrasse 682 Fax: +41-(0)44-430-1101 CH-8048 Zürich mailto:mario * emmenlauer.de Zürich http://www.marssoft.de / http://www.xuvtools.org _______________________________________________ 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... Mario Emmenlauer wrote: Rick Cochran wrote: sed -e '/<key>IFPkgPathMappings<\/key>/,/<\/dict>/d' -e '/<key>IFPkgRelocatedPath<\/key>/,/<string>.\/<\/string>/d' $(NAME).pkg/Contents/Info.plist > Info.plist.sed mv Info.plist.sed $(NAME).pkg/Contents/Info.plist Mario Emmenlauer wrote: Bill Coderre wrote: On Nov 22, 2008, at 10:23 AM, Adil Saleem wrote: Previously i was using Package Maker on Mac OS 10.4 without any problems. Now, for the first time, i have to use the Package Maker (ver 3.0.3) on Mac OS 10.5. I created a package that installs the application in /Applications/MyApp folder. On running the package, it creates the folder MyApp in /Applications folder, but the folder is empty. The application file does not get copied. Any idea why this is happening ? Very likely PackageMaker is turning on the relocation flag due to a longstanding bug. Relocation means that the Installer tries to find an existing copy of your app to update. Say, the one in the source folder that your package is built out of. About a month ago, I wrote a couple of emails explaining how to override this flag -- ripping it out of the appropriate places in the finished package. This email sent to rcc2@cornell.edu This email sent to site_archiver@lists.apple.com