RE: packagemaker install, running instances
RE: packagemaker install, running instances
- Subject: RE: packagemaker install, running instances
- From: "Alex Sheh" <email@hidden>
- Date: Tue, 30 May 2006 18:24:14 -0700
- Thread-topic: packagemaker install, running instances
Thanks Bill, that method works nicely. The potential nib-binary
mismatch is indeed reason to quit the apps.
- Alex
-----Original Message-----
From: Bill Coderre [mailto:email@hidden]
Sent: Tuesday, May 30, 2006 10:39 AM
To: Alex Sheh
Cc: email@hidden
Subject: Re: packagemaker install, running instances
On May 30, 2006, at 10:18 AM, Alex Sheh wrote:
> Does the PackageMaker installer handle contention between a currently
> running program (which may be reading/writing to resources on disk)
> and the installer which needs to overwrite the program files
> (overwrite the same resources)? Or should I simply always terminate
> running instances with a preflight script, or is there some more
> standard way to handle this?
The way I do it is to detect the program running during
InstallationCheck and put up an error asking the user to quit.
There was a lot of discussion about this, but in the end, it's simple
and clear user interaction.
Note that software update does not run InstallationCheck, and preflight
is not allowed to return an error. That's why the (ugly) dialog saying
"Please Quit" with no way to abort the update. If we could avoid that
situation, we would.
As for the first part of the question, I am not sure. I do know that we
have to quit the app because most apps use Nibs, and most of them do not
pre-load the Nibs, but do preload the binary. If the two mismatch,
"hilarity" ensues. (ie. the "quit" menu item no longer works, etc.)
_______________________________________________
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