Re: Explaining why install failed.
Re: Explaining why install failed.
- Subject: Re: Explaining why install failed.
- From: Xochitl Lunde <email@hidden>
- Date: Thu, 11 Mar 2010 17:31:12 -0600
> 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.
>
I'm not using PackageMaker anymore because I wasn't able to get any help
with it before everyone said to use Iceberg. I see that PackageMaker
has an option for Package requirements "Logged-in Users". I
don't see this option in Iceberg. Is it possible to script the check
into the preinstall and be able to get a meaningful response back to the
user if there is a failure? I can't figure out how to get a message
to the user if any of my install scripts fail. I don't get a good
message in my Console.app logs either. It tells me what script failed,
but none of the messages in my script make it through.
Since you've been so kind to answer me, I have another
question as well. When I was using packagemaker, I was trying to
create a check for 64-bit systems. However, the check I created always
failed on my 64-bit systems. I used the "64-bit Instructions Available"
choice, but apparently none of my 64-bit machines can pass the check. Is
this check buggy? What hardware would actually pass the check?
Thanks! _______________________________________________
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