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: Tommy Knowlton <email@hidden>
- Date: Thu, 29 Jul 2004 20:46:55 -0600
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.
_______________________________________________
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.