On Jan 31, 2010, at 12:12, Steinar Bang wrote: >> The files in your woking copy will have permissions based on the umask >> setting of your shell. > > Which is fine if what you want to do is check out software source code, > but for other uses (such as versioning and sharing your home directory), > it isn't very helpful. > > Annoyingly this actually worked in CVS (just chmod go-rwx the RCS file > in the CVS repo). At least for my limited use case which is to limit > read access to files containing security information.
Yes, unfortunately this does not exist in Subversion at this time. FSVS does store file permissions and is based on Subversion, so you may want to look into that. http://fsvs.tigris.org/ > Are there hooks that can be run on the client side when updating, or > checking out from the repository? Not in Subversion itself. Some third-party clients, like TortoiseSVN, implement this, though. > One thing I could do is to write a wrapper script called svn, and put > that in the path...? It could first invoke svn, then, if this is an > update, look for the custom property, and chmod appropriately after the > update. Yes, you could do that.
