Pawel Gega wrote:
> Hello ,
> I develop host integrity monitoring utility and I found the subversion as
> perfect backend for my monitoring daemon.
> The only one problem I really met with my subversion-based host integrity
> monitoring is the '.svn' admin dir in
> working copy path - something quite obvious for source control and
> development, but not for the security monitoring.
> I got round the problem of .svn directories by caching them in the separate
> secured directory. So i used cached .svn dirs
> instead of those real ones in working copies (the monitored directories) when
> doing commits to SVN repo. In that way , some users could even corrupt the
> .svn dirs but they still could not break the working copy.
> I am wondering if you could tell me ,how hard would it be to patch subversion
> code to not to use .svn admin dirs inside working copy (but to be placed
> outside of it).
> I know it is fairly easy to change the name of the admin dir within the source
> code, but would it be hard to change to path to admin directory ? i.e relocate
> it some safe place.
> I just downloaded the latest code from subversion's SVN repo.
Moving the administrative directory is an oft-requested feature. However, due
to the current implementation of the Subversion working copy library,
incorporating this feature into Subversion is non-trivial. We are currently in
the process of rewriting this library in order to decrease the number of .svn
directories in a working copy, and make features such as this possible.
You can see the current design for WC-NG here:
We encourage both testing feedback, as well as input. You're more than welcome
to join in the development efforts to help speed this rewrite to completion.
Received on 2008-12-17 18:49:25 CET