Re: Installation "diverting" under development user
Re: Installation "diverting" under development user
- Subject: Re: Installation "diverting" under development user
- From: Nir Soffer <email@hidden>
- Date: Fri, 22 Feb 2008 22:08:06 +0200
On Feb 6, 2008, at 01:11, Stéphane Sudre wrote:
On Feb 5, 2008, at 11:43 AM, Robert Stainsby wrote:
I've been trying to learn PackageMaker by building an installer for Apple's sample code iSpend app and Spotlight plugin.
Under my (admin) account on my development machine, my built installer won't install the application, despite reporting a successful install. The installer log contains lines like the following, suggesting that it is installing back to the development directory instead of the correct /Applications folder.
Feb 5 21:07:21 Roberts-MBP payloadExtractor[1269]: Diverting "./iSpend.app" to "/Users/robert/Documents/Development/~Build Products/Build Products/Default/iSpend.app"
The installer did install your app, but not in /Applications but in /Users/robert/Documents/Development/~Build Products/Build Products/Default/iSpend.app.
With other accounts on this machine (admin and non), and on another machine, it installs to /Applications as expected.
I haven't made any changes to the default Destination (/Applications) set by PackageMaker when I dragged the iSpend.app bundle into it.
Is this expected behaviour, or am I doing something wrong?
I believe this is a known big bug in PackageMaker 3 (locator getting re-enabled in your back).
It happens when you use relative paths in packagemaker, which is necessary if you want to build the package on different machines.
My current workaround is to disable relocation in the built packages with a script that run after packagemaker.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden