Monte Benaresh <email@hidden> wrote on 08/19/2010
> Hi Xochitl, >
> Just to clarify, we are using Iceberg to create bundle install
> packages for Installer.app. The code I am writing is indeed
> preflight script. >
> We have been able to fail the install just fine from the preflight
> script by executing "exit 1". But as you said, we
have no way of
> putting up a message to the user, though we emit useful messages to
the log. >
> Thanks for the pointer to the UNIX domain sockets check code. We
> actually use that code in our daemon to set up the socket files.
> But during install, we are trying to follow the recommendations in
> TN 2083 for the daemon itself. The questions I am bringing up
> reflect problems our beta testers have encountered. >
> Thanks, > Monte >
> On Aug 19, 2010, at 2:39 PM, Xochitl Lunde wrote: >
It should be easy to create a volume check or installation
check if you are using Iceberg. With either of these checks you are
able to present a meaningful message to the user. If you make a preflight
failure, the installer will fail, that is true. I saw that in my
testing also. Mr. Peelman has some good information about packages
and how to make InstallationCheck give a nice error message.
Or you could use a volume check to show that some
volumes with bad permissions are not suitable destinations. This
is just one idea, of course, and it doesn't sound like it matches your
preference, but there it is.
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