On Aug 15, 2006, at 10:22, Hadmut Danisch wrote:
> I tried to keep some confidential data in configuration files (secret
> keys, passwords and things like that) kept in a SVN repository, but
> found that svn modifies the file permissions when updating:
>
> % dir
> total 8
> -rw------- 1 danisch users 29 2006-08-15 10:12 x1
> -rwx------ 1 danisch users 29 2006-08-15 10:12 x2*
>
> % svn update
> U x1
> U x2
> Updated to revision 2.
>
> % dir
> total 8
> -rw-r----- 1 danisch users 58 2006-08-15 10:12 x1
> -rwxr-x--- 1 danisch users 58 2006-08-15 10:12 x2*
>
>
> Which is a pretty bad behavior. SVN should never change the permission
> of existing files. It should either leave them as they are (problem:
> what happens if a file is marked executable in the repository?) or
> allow to specify permissions as properties.
>
> And if the file is unreadable, the copy in .svn should be as well.
>
>
> I guess similar problems exist with ACLs and Windows permisssions.
I'm not sure Subversion was designed for this case. It certainly does
not attempt to remember file permissions. If you want that in
Subversion, someone has made a branch that includes this
functionality. You'd have to build it yourself. It's the owner-group-
mode branch here:
http://svn.collab.net/repos/svn/branches/meta-data-versioning/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 15 14:15:57 2006