Re: Different "Quit App" behavior between PackageMaker.app and cmd line
Re: Different "Quit App" behavior between PackageMaker.app and cmd line
- Subject: Re: Different "Quit App" behavior between PackageMaker.app and cmd line
- From: Matt Ronge <email@hidden>
- Date: Sun, 21 Feb 2010 13:42:18 -0600
On Feb 18, 2010, at 4:14 PM, Iceberg-Dev wrote:
>
> On Feb 18, 2010, at 3:08 AM, Matt Ronge wrote:
>
>> Hi,
>>
>> I'm having a strange problem with PackageMaker. My installer makes sure an app (Mail in this case) is not running, and if it does, quits it. I used the Actions tab of PackageMaker to build this action. It is a "Get App" attached to a "Quit App".
>>
>> Now here is where it gets strange... If build the installer with PackageMaker.app, it works great. If Mail is running it quits it and proceeds with with installation. HOWEVER if I build the installer with the command line tool /Developer/usr/bin/packagemaker, it installs but it WON'T quit Mail if it's running. It just leaves it running and does the install anyway.
>>
>> Why the difference in behavior? I use this to build on the cmd line: "/Developer/usr/bin/packagemaker -d installer/myinstaller.pmdoc -o build/MyInstaller.pkg"
>
> Have you checked if there's any difference between the package you get when you use the UI and the one you get when you use the command line?
I extracted the contents of both packages using Pacifist. The one built using the UI has a preflight.pkg inside of it, while the command line one doesn't. So they are very clearly different. Has anyone seen this before?
--
Matt Ronge
Founder
Central Atomics
Makers of Rocketbox!
http://www.getrocketbox.com
email@hidden
_______________________________________________
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