Re: Explaining why install failed.
Re: Explaining why install failed.
- Subject: Re: Explaining why install failed.
- From: Iceberg-Dev <email@hidden>
- Date: Sat, 13 Mar 2010 00:55:56 +0100
On Mar 12, 2010, at 3:35 PM, sakshi wrote:
Hi Bill,
Can you elaborate on this? There are times when installation checks
are too complicated to be a part of volumecheck(). What is one to
do in such a case?
For example, the case I heard of recently was one where the team
had a complicated logic to detect whether an app was in use or not.
This logic was placed in a binary and the binary was invoked as a
preinstall step of the first component package. How can they
address this case since invoking custom binaries is not possible in
the volumecheck() phase?
Btw, to augment my knowledge: is failing in postinstall supported?
Failing "works" for preflight as far as I can see on Mac OS X 10.4.11.
If a preflight exits with -1 for instance, the installation will stop.
But the error messages are not user friendly:
"There were errors installing the software"
"Please try installing again."
This might be what unsupported is referring to.
_______________________________________________
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