>>>>> Tyler Roscoe <ty...@cryptio.net>:
> Subversion doesn't track file permissions in this way.
Yes, looking closer at the thread I found, it is a patch that was shot
down in February 2005
http://svn.haxx.se/dev/archive-2005-02/index.shtml#5
> 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.
Are there hooks that can be run on the client side when updating, or
checking out from the repository?
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.
It won't help me if I run a client that's linked with the svn .so/dll,
or implements the svn protocol in a different language.
