site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Cormac, Best, Luke On Mar 31, 2007, at 8:20 AM, Cormac Daly wrote: Hi All, Hope all this is clear, and any suggestions would be appreciated, Thanks, Cormac _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/luke%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Why do you need to use 2 different packaging solutions in tandem? Is there a way that you could alter the process to just use Apple's Installer? I'd be interested to know the specifics of the problem you're trying to solve. My product will incorporate a 3rd party plug-in - this will have its own ViseX installer. My product uses a PackageMaker solution and I wish to launch the ViseX installer from mine. I can sucessfully do this using a preflight or preinstall shell script. The ViseX installer will require the user to specify an installation directory (whose location will be written to a plist file) at install-time and the installer for my application will need to read this at a later point to ensure that components of its installation are put in the same location as the plug-in. The ViseX installer must therefore finish running before my installer proceeds to install its own files. However, when the ViseX installer is called the PackageMaker installer is still visible and active, albeit not in focus. It is therefore possible for the user to continue using the PackageMaker installer before the ViseX installer has finished, in which case the installation process will not run correctly. Its possible to put explanatory text in PackageMaker's readme/ welcome window but this not ideal. I was wondering if its possible to somehow disable the PackageMaker installer until the ViseX installer has sucessfully finished running? This issue may concern shell scripting more than it does installers in general but I thought this might be a good place to ask. This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com