Ben Collins-Sussman wrote:
> Ralph Becket wrote:
>
>> My problem is that I checked some files into my Subversion repository
>> and now I want to change the permissions on them such that next time I
>> check them out these files are neither group nor world readable.
>> Simply chmodding the files and then doing `svn ci' doesn't achieve
>> anything.
>>
>> My question: is there a simple solution?
>>
>
> No, svn has no system for preserving permissions, or tweaking them.
> The only feature that is "close" is setting the svn:executable
> property, which causes files to be +x in the working copy.
>
Depending on what you classify as a simple solution you could possibly
get the desired effect by using a wrapper script that sets the umask to
block group and other access (haven't tried it myself so may or may not
work) the other approach is to use svn properties to record what the
file permissions should be and have a script that does the chmod after
a checkout. Have a look at
http://www.contactor.se/~dast/svnusers/archive-2003-08/0255.shtml
<http://www.contactor.se/%7Edast/svnusers/archive-2003-08/0255.shtml>
for a version I wrote last year.
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 15 06:38:22 2004