site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Mark, On Oct 22, 2006, at 10:47 AM, Mark Krenek wrote: The dilemma this introduces for non-admin accounts is two-fold: Thanks, Luke Mark Krenek Development Manager Aspyr Media _______________________________________________ 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/luke%40apple.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... I am writing an installer that patches an existing game of ours. Our software was originally drag-installed by the user. I don't know if the user was an admin account or not. I don't know where they installed the software. What that means is that they could have installed it in a location requiring admin privileges, like / Applications. Therefore, it seems that I must set my package up to require Admin Authorization. Otherwise it will fail if the software is currently installed in an admin location and the installer is being run by a non-admin user. (1) If a non-admin user originally installed the software in a non- admin location, like his home folder, then our installer still asks him to type in an admin password. The user didn't need an admin password to drag-install the original game, but now they do for the patch! (2) The installer sets the ownership of all the files installed by the patch to the admin account, not the user account. That means that the files that were part of the original drag-install have owner set to the non-admin user but new files installed by the patch have the owner set to the admin account. Is there any way around this? To recap, this is only a problem when the installer package is set up to require Admin Authorization. This was done because there's a chance the original installation occurred in an admin location. One way to solve this problem using the tools at hand is to make a distribution that has 2 choices: One with a package that requires admin authorization and one that doesn't. You can use locator & other Javascript logic to determine the ownership of the directory in which the game was drag-installed, and then set up your choices to install the appropriate package. The downsides are that this will only work for 10.4 and later, and that you will ship twice the bits, since it will require 2 copies of the update package to be shipped. Hopefully it's a small patch. This is a case the Installer team should investigate going forward. Can you please file an enhancement request for better support of cases like this? (http://bugreporter.apple.com) This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com