Reputation: 49321
I'd like some clarity on linux permission inheritance and subversion. If I check something out that is owned by "svn:svn" and commit it, then, run svn update on a directory that was originally checked out, the file(s) gets MY permissions. I am a member of group svn. Could I remove myself from the svn group to force the permissions to stay svn:svn when I do an update? I am using an Subversion client to check out the files and this uses svn as the user. Thanks
Upvotes: 3
Views: 1190
Reputation: 360572
You can set the group sticky bit on the parent directory, which'll auto-assign that directory to any NEW files created in there
chmod g+s .
I don't think it'll apply the sticky bit to any subdirectories, so you'd have to replicate this for each sub-dir, but at least the files will come out with the proper group ownership.
Upvotes: 1
Reputation: 81674
Subversion doesn't store file ownership or permissions in the repository. If you check something out, it's owned by you. I'm not sure what it is you're trying to accomplish, but it's going to involve a script to change file ownerships on your local machine.
Upvotes: 0
Reputation: 711
You need to set the sticky bit on the group permissions on that directory.
chmod g+S svndir
This will force the group permissions do be inherited by it's descendants.
Upvotes: 3