RE: Packages: Issues with 10.2 Installer App
RE: Packages: Issues with 10.2 Installer App
- Subject: RE: Packages: Issues with 10.2 Installer App
- From: "Huyler, Christopher M" <email@hidden>
- Date: Fri, 8 Oct 2004 13:27:40 -0400
- Thread-topic: Packages: Issues with 10.2 Installer App
Thanks!
I will incrementally upgrade my system to 10.2.8 and see if/when this
bug gets fixed. I just wanted to check to see if anyone else has seen
this and knew more about it. I have seen my install fail on 10.3 and
I'm pretty sure I saw a failure on 10.2.? when I first created my
package and tested it over a year ago. I guess I never tried it on base
10.2 install.
We currently have a separate tool that gets launched over the Installer
to configure additional settings. A simple error display tool is a good
idea though. I will keep that in mind for our next release.
Killing the Installer app seems kind of risky although it's probably the
only solution that won't confuse the user. I will see what version this
bug is fixed before I try to implement something like that.
~ Chris
-----Original Message-----
From: stephane sudre [mailto:email@hidden]
Sent: Friday, October 08, 2004 1:13 PM
To: Huyler, Christopher M
Cc: email@hidden
Subject: Re: Packages: Issues with 10.2 Installer App
On Oct 8, 2004, at 5:31 PM, Huyler, Christopher M wrote:
> I have some basic shell scripts that I use during my package install,
> preflight and postflight. I was running some tests on a fresh 10.2.0
> system and even though the postflight script failed and returned 1,
the
> Installer Application said the software installed successfully. I
> tried
> changing postflight to postinstall/postupgrade to see if that made a
> difference but it didn't.
>
> Am I doing something wrong or is the 10.2 Installer Application
broken?
> Shouldn't the install fail if anything other than 0 is returned?
Stupid question: is this working on later versions of 10.2 or
Installer.app?
Because if it is, then it was a bug which got fixed. So your only hope
is to find a workaround:
a really stupid one which comes to my mind is to kill the Installer pid
and display an alert from the preflight script. Haven't tested it
though.
> Also, I noticed that you can display a message when something fails in
> the InstallationCheck script by making an InstallationCheck.strings
> file. Can you do the same for the other scripts? It would be
> nice...the more customizable an install using Installer is, the easier
> it will be for Developers to adopt the package technology.
You can for VolumeCheck but not for other scripts.
One possible solution involves using a secondary tool using the
CFUserNotification API from the CoreFoundation framework from the
Script.
BTW, there's a new installler-dev mailing list hosted by Apple:
http://lists.apple.com/mailman/listinfo/installer-dev
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden