• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Quitting the Installer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Quitting the Installer


  • Subject: Re: Quitting the Installer
  • From: development2 <email@hidden>
  • Date: Tue, 28 Oct 2008 07:34:32 -0600

Thanks,
On Oct 28, 2008, at 7:03 AM, David Watson wrote:

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.

Well it won't work right if they run it from the Command Line. This is an installer for basically a Windows Software Company and they want it as much like there Windows installer as possible. I brought thus up to them and they siad well it just won't work if they run it front he Command line.


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.

Well we have to quit the installer because that is what the Windows version does in the case that the new hardware can not be found. I wanted to tell the user to to rectify the problem, and then we would try again to find the device again, but they don't want me to do that. They just want the installer to bail. Not worth the fight in this case. I need the job. :)




But I suppose if you really, really, wanted to, you could just call the exit() C function, or system("killall Installer.app").

Yeah I could dot that.

Thanks,



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
  • Follow-Ups:
    • Re: Quitting the Installer
      • From: Greg Neagle <email@hidden>
References: 
 >Quitting the Installer (From: development2 <email@hidden>)
 >Re: Quitting the Installer (From: David Watson <email@hidden>)

  • Prev by Date: Re: Quitting the Installer
  • Next by Date: Re: Quitting the Installer
  • Previous by thread: Re: Quitting the Installer
  • Next by thread: Re: Quitting the Installer
  • Index(es):
    • Date
    • Thread