➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients brian.curtin, carlfk, dsmiller, ezio.melotti, flox, jaraco, loewis, mel, mhammond, michael.foord, nnorwitz, norvellspearman, r.david.murray, tim.peters
Date 2010-03-02.22:51:38
SpamBayes Score 4.649571e-05
Marked as misclassified No
Message-id <4B8D9678.8070801@v.loewis.de>
In-reply-to <1267569582.89.0.77569108195.issue1284316@psf.upfronthosting.co.za>
Content 
> Martin: Would it be sufficient to copy the ACLs from %programfiles%,
> or would it be better to hard-code the permissions from
> %programfiles% from a known standard configuration? Is it known if
> the ACLs on %programfiles% in WinXP differ from later platforms? What
> difficulty have you encountered?

I can only answer the last question: I tried using the ACL features in
MSI (i.e. with the LockPermissions table), and couldn't get that to work.

Personally, I would think that restricting write access to the user
performing the installation should be good enough.
History
Date User Action Args
2010-03-02 22:51:40loewissetrecipients: + loewis, tim.peters, mhammond, nnorwitz, jaraco, mel, dsmiller, norvellspearman, carlfk, ezio.melotti, r.david.murray, michael.foord, brian.curtin, flox
2010-03-02 22:51:38loewislinkissue1284316 messages
2010-03-02 22:51:38loewiscreate