Sebastien,
I use svn to record entire filesystems by using the svn properties,
marvelous invention these things. Though the use of a shell wrapper
around svn I record ownership, permission, devices and symlinks (enough
to recreate a full system) plus by enabling 'use-commit-times' in the
config the results are a good recreation of the original filesystem.
I emailed the script awhile back and you can find it at
http://www.contactor.se/~dast/svnusers/archive-2003-08/0255.shtml . I
would not want to say the script is 100% correct or the most efficient
but I find it works quite well for me. The only real issue I know is
that the name space for the properties could have been chosen a little
better and there may be an issue if you convert a symlink back to a file
it doesn't detect that the symlink has gone and on the next asvn update
the file gets deleted as it creates the symlink. The easy work around is
with the symlink and file deleted run 'asvn ci', you don't have to
commit it, and it will stop trying to create the symlink. A svn update
will restore the file and everything is happy again.
The only other problem I have had is in a few cases when I have been
merging filesystems property changes don't always work when you do an
update after the checkin. I find occasionally I have to delete the
entire directory and do another update to get the correct properties
from the repository. If I can produce it as a reproducible problem I
will. The problem appears to be when a property is deleted. I've found I
can have two working copies of the same repository both at the same
revision but one will have a property that the other doesn't. If I
delete the directory and and an update the property is not restored.
That is just something to be careful of.
Ross
Sebastien Cevey wrote:
>Hello
>
>My question is, is there a way to save (probably in the repository)
>the permission bits of a file ?
>
><snip>
>The question is especially related to cases where RCS is used to
>maintain configuration files which are expected to have a given
>permission (eg. no read permission for 'other').
>
>
>Thank you !
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 12 02:19:09 2003