site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com thanks for the responses, everyone. -- John Gee, ADInstruments Programmers live in interesting times... _______________________________________________ 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... forgive me for saying this, but even if something called "allow relocation" is on, especially by default, it should not allow overwriting other applications or random directories under one's home directory. particularly if that wasn't the default behaviour under earlier versions of the installer or package maker. that's a bug, and it's probably the biggest bug i've encountered in my time in software. on a related note, i set the destination directory for all my installer targets to /Applications. since the advent of Unix-ish path syntax, ie circa 1970, that's been an absolute path. still, when i selected "absolute path" off the accompanying popup menu, the package maker app decided to select both "absolute path" and "relative path" options on the menu, and change that /Applications destination path to a relative path (ie ../../../../../Applications or somesuch). that's a bug too, and it's almost as big. i'm still wondering why Apple chose to change a working application - the earlier package maker, with its convenient command-line version, which worked just fine thanks - into the current version, which has devastated various application environments on my disk and invalidated all previous installer package files and ant scripts etc, into the bargain. anyone from the Apple package maker or installer teams on this list? state your case. my support for the Mac platform is in question thanks to this situation. At 11:40 AM +1300 10/1/08, John Gee wrote: The default behaviour for applications added to projects is that they are "relocatable". This does not work well on development computers, where there are routinely multiple versions, including the version freshly built. Look in the "Components" tab of the project contents for the "Allow Relocation" checkbox column, and try turning that off. On a closely related note, you may discover after changing the setting that it will not stick. In that case, switching the contents from project relative paths to absolute paths is likely to make the setting stick. This email sent to site_archiver@lists.apple.com