site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Peter, Hello Mike, Sunday, May 13, 2007, 1:23:51 AM, you wrote: For example, in one project, for which I wrote an installer, the installed software is basically a UNIX daemon + additional supporting files. But it also needs an Installer Plugin for entering the license number (it is commercial software) and choosing some options which would be very awkward to do at any other point in time or through any other method. Why not simply make a small program that pops up a dialog for the user to enter the code, and then run this in your installers Postflight script ? Not really an issue for my specific case at the moment. Thanks! Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Note: I read this list in digest mode! Send me a private copy for faster responses. _______________________________________________ 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... Am 14.05.2007 um 21:05 schrieb Peter Mulholland <darkmatter@blueyonder.co.uk>: Well for one it would force the user to enter data during the actual install. Secondly it doesn't really help with the ARD or CLI cases AFAICT. Third, the Installer Plugin is already implemented ;-) That will work on 10.3 and earlier as well, then. Anyway, I'm more interested in a general answer to my question of how to reconcile the need for additional user input with ARD or CLI installs. I have a working solution for the case where Installer Plugins (or other interactive GUI) are possible. It's probably easier than writing an Installer Plugin too (trivial with NIB files for the GUI) Writing an Installer Plugin was very easy as well. With better documentation (or any at all) it would be just as trivial. This email sent to site_archiver@lists.apple.com