I checked out the ActivePython[1] installer just now. Two things are noteworthy:
(1) It installed as a non-admin.
This was an over site on my part. This issue is fixed. Consider it closed.
It even installed file associations as "per
user" as described in http://support.microsoft.com/kb/257592 .
Great I will do that. Thanks.
(2) In the list of installation features, one of the options is named "Register
as Default Python". This feature installs global settings such as PATH vars and
file associations. It is enabled by default for both admins and non-admins but
can be disabled (e.g. perhaps the user normally wants to use a different
interpreter instead).
Maybe this can come later. It could help control the path for upgrades.
> This will make the installer much more difficult
> to code and maintain.
I don't believe you. :)
Well I have made great strides since we last talked, and yes I will get this to work, but it does involve a lot of scripting. This does increase the complexity. Not to an unmanageable amount, but it does make a difference.
I think InnoSetup's IsAdminLoggedOn() will do. This may require extra care on
Vista concerning privilege elevation (a search for "IsAdminLoggedOn Vista" in
the InnoSetup newsgroup archives brings up some discussions on this).
Well this is what I am using. I also know and use INNO Setup often. ;)
Something I've seen other installers do (e.g. the Cygwin installer[2]) is
provide an explicit option to install either for "All Users" or for only the
"Current User" (Just Me). So, you don't necessarily need to check for
IsAdminLoggedOn(). In fact, it may be more correct to provide this as an
explicit option in case an administrator wants to install only to one's own
account and not for all users. Checking IsAdminLoggedOn() might still be useful
though to catch a non-admin attempting to install globally (assuming that would
remain correct on Vista).
