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.
The dilemma this introduces for non-admin accounts is two-fold:
(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.
Mark Krenek Development Manager Aspyr Media
|