site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com This is somehow how Safari is doing for the acknowledgements. http://lists.apple.com/archives/installer-dev/2006/Jan/msg00058.html Thanks in advance, Dan -- Dan Nigrin Defective Records 202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X http://www.defectiverecords.com http://www.jackosx.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... Aggregate the ReadMe and License files into one ReadMe and one License file and put them in the root metapackage? Since you need to run on 10.3, an Installer Plugin would not do any good. Stéphane, thanks for the response - although this is a straightforward option, the reason I want to do it the way I originally described is because one of the packages is from a different software provider. They have given me the permission to bundle their installer within mine, but I would much prefer not to "mess" at all with their installer, in order to keep the separation of "their" stuff from "my stuff" fairly clean... In the interim, I did find a previous post on the list covering some of the same ground: I'm interested in further exploring the bit that says "I suppose it's also possible to chain several installers together, such that when the user finishes one installer, the next is automatically launched." Could anyone suggest an approach to how I could do this, with the following constraints: * Only one installer package visible to end user * Run a postflight script after both pacakges installed, but which is currently NOT part of the second package (and which is the other software provider's, so I would like to not add anything to their package). This email sent to site_archiver@lists.apple.com