site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com hey Karl, thanks for your detailed informative response. regards j _______________________________________________ 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 would be really careful about doing things like this. There are three reasons for this: all the scenarios you describe happen, i'm sure. however the most common scenario for our application is, by far, a user sitting at home doing a local install affecting the environment of the user who is currently logged in. If you absolutely have to have it, then you probably should look into writing yourself into /Library/Preferences/loginwindow.plist, namely inside the AutoLaunchedApplicationDictionary item (it should be an array). It you can't justify putting yourself in that file, then you should not have your installer do this. as i understand it, writing to /Library/Preferences/loginwindow.plist would activate this for all users. if a machine is shared between users, then i want the run-at-login component to run only for those users who have run the installer. i will have time to revisit this in the future but for right now i have to go with the simple solution for the most common scenario. all this could have been avoided by a checkbox in PackageMaker. then the Installer could ask the user whether it's OK to do it, etc. this is a simple requirement that has been massively overcomplicated -- IMHO. This email sent to site_archiver@lists.apple.com