site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On lundi, août 27, 2007, at 05:56 PM, Dallas Jones wrote: Hi there - Is there another approach, or do I just need to get over the legacy document warning? _______________________________________________ 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... I want to be able to install one of two packages as part of a metapackage depending on whether a file is found. I have edited the packages to add a package requirement; one of them will install if the file is found; the other will not install if the file is found. This didn't work - the installation fails if the requirements for either of the packages fails. It looks like I can do what I want to do with an InstallationCheck script - and I see some examples in the list archives. My concern with this approach is the big floating Legacy Document warning on the InstallationCheck page on the Apple site. Thanks in advance for any opinions... What is the big legacy warning? Is it the "this package contains a program that determines if the software can be installed. Are you sure want to continue?" warning? If it's really a trouble for you, one solution could be to write a quick Cocoa (or another language) Front-End to determine which package should installed, add the packages in the resources and voilà! You could even stick a Package icon on the application if you really want it to look like a package. This email sent to site_archiver@lists.apple.com