Re: How can I set permissions on shared source files?
Re: How can I set permissions on shared source files?
- Subject: Re: How can I set permissions on shared source files?
- From: Julian Vrieslander <email@hidden>
- Date: Fri, 30 Jul 2004 13:20:05 -0700
- Fnork: garbanzo
Thanks for the suggestion, TK. NetInfo Manager is not exactly transparent
to a unix-challenged person, and I could not figure out how to create a new
group. But google led me to a tutorial that showed how to add users to the
staff group
<http://captnswing.net/howto/iphoto/>
and that's what I tried. I then changed the permissions on my
"~/Public/Projects/" folder, as per your suggestion.
Your solution does only part of what I was seeking. Existing files in that
folder are read/write enabled for everyone in staff group. But new files
added to the folder are not. I still need to change permissions on those
files, or re-run the recursive command to change permissions for everything
in the folder.
Mac OS X Server has a feature which allows the admin to modify the standard
unix permissions behavior so that items added to a folder take on the
permissions of the folder. But apparently this is not possible in Mac OS X
(non-server).
Does anyone know another solution?
- JV
On 7/29/04 7:46 PM, "Tommy Knowlton" <email@hidden> wrote:
> You can create a unix group e.g., develop, using NetInfo Manager, and
> then add all the appropriate users to the group (again using NetInfo
> Manager). Then, from a Terminal.app shell prompt, do 'chgrp -R develop
> path/to/the/working/directory' and 'chmod -R g+rw
> path/to/the/working/directory', and you should be on your way. Note the
> "-R" option to both commands simply makes the command recursive,
> therefore affecting the contents of the directory and subdirectories.
>
> HTH,
> --
> Tk!
>
> On Jul 29, 2004, at 17:21, Julian Vrieslander wrote:
>
>> This may be a trivially simple issue. But I do not have a unix background,
>> and our (usually-unix-savvy) sysadmin was stumped, too.
>>
>> I need to share some Xcode projects with colleagues in the same office. My
>> first idea was to put copies of the project folders in my public folder
>>
>> ~/Public/Projects/
>>
>> Colleagues log into my Mac as guest, and copy the files to their own Macs.
>> But the files still have permissions set to (-rw-r--r--), with me as owner.
>> Before they can edit them in Xcode, they have to change the permissions. Is
>> there a simple way to get around this?
>>
>> One idea is to configure the ~/Public/Projects/ folder so that when files and
>> folders are dropped into it, they take on unrestricted permissions
>> -rwxrwxrwx. I tried twiddling the permssion bits on the folder with the
>> Finder's "Get Info" window. Did not work. Our sysadmin suggested some
>> terminal commands
>>
>> chmod -R o+rw ~/Public/Projects/ chmod -o+S ~/Public/Projects/
>>
>> Did not work.
>>
>> A google search found other people asking the same question, and some
>> suggestions to use an Applescript Folder Action. But there are reports that
>> this is unreliable, since Folder Actions (allegedly) do not detect changes
>> within folders nested below the monitored folder.
>>
>> Sysadmin also suggested creating a group for all the people using these
>> projects. But wouldn't that require me to change the permissions on all the
>> files that I share? I could edit my umask, but that would affect ALL the
>> files I create, and I don't know if there are security implications to that.
>>
>> How do other folks deal with this? Maybe version-control systems help with
>> this issue, but that's probably way too much complexity for us - we have all
>> we can handle, just trying to learn unix, OS X, and Xcode.
--
Julian Vrieslander <email@hidden>
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.