Skip Menu |
 

This queue is for tickets about the Perl-Dist-Strawberry CPAN distribution.

Report information
The Basics
Id: 50323
Status: rejected
Priority: 0/
Queue: Perl-Dist-Strawberry

People
Owner: Nobody in particular
Requestors: kmx [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: MSI installer - is <Condition ...>Privileged</Condition> necessary?
Download (untitled) / with headers
text/plain 810b
Hi, I have a question concerning MSI installer. I am in doubts why it is necessary to have this section in Main.wxs: <Condition Message="You need to be an administrator to install this product."> Privileged </Condition> As IMHO the the installer in fact does not necessarily need Admin privileges: - new dir c:\strawbery can be created by common User - when c:\strawbery is created by User than it is also writeable by User - we are not setting *.pl associations (this would require Admin priv) - env variables can be set only User-wide if not running as Admin On the other hand if c:\strawberry is not writeable by current user the installer throws another error message saying that user has not enough permissions. Are there any other reasons why we force <Condition ...>Privileged</Condition>? -- kmx
Download (untitled) / with headers
text/plain 185b
I have prepared here: http://svn.ali.as/cpan/users/kmx/wix3-test/ a proof-of-concept .wxs script + sample .msi handling "Admin" vs. "non-Admin" situation Any feedback welcome. -- kmx
Download (untitled) / with headers
text/plain 1.9k
On Thu Oct 08 06:30:13 2009, KMX wrote: Show quoted text
> Hi, > > I have a question concerning MSI installer. > > I am in doubts why it is necessary to have this section in Main.wxs: > > <Condition Message="You need to be an administrator to install this > product."> > Privileged > </Condition>
I was being conservative. I can't recall if the .exe installers did the same thing - I thought they did. Show quoted text
> As IMHO the the installer in fact does not necessarily need Admin > privileges: > - new dir c:\strawbery can be created by common User > - when c:\strawbery is created by User than it is also writeable by User > - we are not setting *.pl associations (this would require Admin priv) > - env variables can be set only User-wide if not running as Admin > > On the other hand if c:\strawberry is not writeable by current user the > installer throws another error message saying that user has not enough > permissions. > > Are there any other reasons why we force <Condition > ...>Privileged</Condition>?
The start menu options are currently "all-users" as well. To take the admin check out, I'd want to make sure of these three things, in addition to the ones mentioned above: 1) I would want to check for the situation in which two non-admin users tried to install Strawberry, with the result being that the second time either errors out or just installs the start menu/environment stuff. 2) Then define proper behavior and implement it for when an admin and a non-admin both try and install it, either the admin first or the non-admin. 3) I've also been told that CPAN.pm does not work well for non-administrators at the present time. [I could be wrong.] I don't see me getting the time to test all of this within the next week, so putting this off until after the October release. Not that it's not important, it's just that I'm minus on the minutes required before then, and I'd want more testing even if I had the minutes than switching it on right before RC1 would do. Okay, KMX? --Curtis


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.