site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Aug 6, 2009, at 1:42 PM, Howard Moon wrote: You skip them. -Greg _______________________________________________ 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... good points all, but our software is not something that is generally installed by system administrators, Hmm. I've had to wrestle a lots of audio plugins for ProTools machines. I'd much rather use the same system I already use to manage installs than have to visit the user and do a manual install. It's more likely the machine will get timely updates of the software if I can use my normal methods of installation. or in the background. (How would you handle the "normal" dialogs, like the license file and acknowledgement, read-me, etc., if run that way?) They're audio plug-ins (and supporting documentation files, etc.), and they run inside audio hosts. We need to be able to run an authorization application at the end of the installs to make it easier for users to authorize their software, and we can't do this from within the hosts. So, prior to running the authorization app, we display a message that says that the installation has completed and that the authorization app will run when they hit Continue. When run via command-line, you'd skip this, and the administrator would be responsible for running the authorization app separately. It's laudable to make things easy for the average end-user doing a manual install, but don't make it impossible for an admin to do an automated/remote install. This email sent to site_archiver@lists.apple.com