PackageMaker plugin -- Programmatically disable (unselect/hide) packages
PackageMaker plugin -- Programmatically disable (unselect/hide) packages
- Subject: PackageMaker plugin -- Programmatically disable (unselect/hide) packages
- From: Joel May <email@hidden>
- Date: Sun, 14 Feb 2010 01:06:30 -0600
I have one of those situations where I need the registration number during the install. Based on the reg number, either the network version or the desktop version of the software is installed. The fact that both products exist on one CD is disguised from the user. This is for saving money on manufacturing, stocking, etc.
This is the way it's been forever and I have to keep this behavior. I've been using InstallerVise, but I really hate it and want to move on to a modern installer, i.e. PackageMaker.
I cannot figure out how to disable a subpackage via the plugin. There is hardly any api or communication back into the installer from the plugin.
I've tried some hacky method by writing tag files to the temp directory so the requirements check or install scripts could use this information. However, the requirements check scripts run before the plugin, so that does me no good. And the install scripts are unable to stop a sub-package from installing. If they exit with a fail code, they kill the install entirely rather than just disable the package.
Am I missing something? Is there some clever way to do this? Is there a way for the plugin to do anything other than display a UI and write files -- can it talk back to PackageMaker?
Does Iceberg handle things differently or does it have the same limitations as PackageMaker?
Thanks,
Joel _______________________________________________
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