Re: Explaining why install failed.
Re: Explaining why install failed.
- Subject: Re: Explaining why install failed.
- From: sakshi <email@hidden>
- Date: Fri, 12 Mar 2010 20:05:05 +0530
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?
Thanks,
Sakshi
On Fri, Mar 12, 2010 at 4:07 AM, Bill Coderre
<email@hidden> wrote:
On Mar 11, 2010, at 1:28 PM, Xochitl Lunde wrote:
I have a preflight script now which
checks if more than one user is logged in and will fail if additional users
are logged in. I am using Iceberg to create my package, and my script
is just a basic shell script. How can I get a message back to the
installer that says something about why the install failed?
No. As a matter of fact, failing during a preflight is NOT SUPPORTED. Please do your testing in InstallationCheck/VolumeCheck.
_______________________________________________
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
_______________________________________________
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