Re: Xcode default "Install Permissions", clean "permission denied"
Re: Xcode default "Install Permissions", clean "permission denied"
- Subject: Re: Xcode default "Install Permissions", clean "permission denied"
- From: Greg Guerin <email@hidden>
- Date: Wed, 22 Aug 2007 20:08:09 -0700
Alex Sheh wrote:
>The main issue is that when I try to clean the configuration, Xcode
>needs to be able to "rm" the previously built Bundle.app. However,
>Xcode can't do this because the folders aren't writable, and the clean
>fails. So basically developers can't clean from within Xcode and have
>to manually remove the folder themselves, which doesn't make for an
>efficient workflow.
Why not just change the permissions used by the install phase?
The default is:
a-w,a+rX
Change it to:
go-w,a+rX
which will retain write permission for the owner, but forbid writes by
group or others.
Examining the default permissions (a-w,a+rX), they look to me like they're
intended for a real public deployment. Public deployments don't seem like
the kind of thing I'd want removed when doing a Clean build in Xcode, but
YMMV.
If I did want a public deployment removed, I'd either create a separate
target that removed the deployment (recursive chmod then recursive rm)
before doing the install again, or I'd just change the original deployment
permissions to retain writes by owner.
Disallowing writes by owner is a pretty small obstacle anyway. The owner
always has the ability to change permissions to allow writes, which then
allows recursive removal. So "a-w" isn't doing much, except acting as a
minor speed-bump to reckless removal. Since it's also interfering with the
Clean, which you deem more important, just eliminate the speed-bump you
don't want, and the problem is solved.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden