Re: Quitting the Installer
Re: Quitting the Installer
- Subject: Re: Quitting the Installer
- From: David Watson <email@hidden>
- Date: Tue, 28 Oct 2008 09:03:57 -0400
Keep in mind that users may not use the GUI installer at all, or they
may modify your package to remove your plugin. Because of this, you'll
need to support doing whatever kinds of checks/setup are necessary on
first run of your app, as well.
If you haven't used the command-line installer, you can invoke it like
this:
sudo installer -target / -pkg mypackage.pkg
I suppose it's possible that you could have your installer plugin
create a specific magic file and have your preflight script check for
it, but that seems a little hacky.
Also, why do you need to quit the installer at all? Your plugin should
be able to prevent the user from clicking "next". That way you give
them the option of rectifying the problem, instead of just forcibly
exiting.
But I suppose if you really, really, wanted to, you could just call
the exit() C function, or system("killall Installer.app").
On Oct 28, 2008, at 8:20 AM, development2 wrote:
Is there anyway to make a Package Maker Installer Quit. I have a
need if the user does not have the right setup or there hardware
that we are installing for is not connected I need to force quit the
Installer. Now I have written several plugins that do some things we
need to do during the install, but if there hardware is not
connected I need to give them a message why, and quit the app.
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