On Thu, Aug 7, 2008 at 10:15, Paul R <paul.r.ml_at_gmail.com> wrote:
> Hello dear subversion users list,
>
> We are about to provide a service in which companies use SubVersion to
> synchronize their files. Those files, mainly Word and Excel files,
> will all be considered as binary so file content is not likely to be
> mergeable at all. To avoid endless conflicts resolution for non-tech
> peoples, we want to be able to automatically activate property
> need-lock on every files added to the repository. Yes, this is
> a non-orthodox use case of SubVersion. I read the following post
> http://svn.haxx.se/users/archive-2006-04/0415.shtml but the given
> solution implies client-side settings, which is not an option for our
> case. I am really looking for a server-side solution.
Subversion has no server-controlled "global" configuration. The
solution for this is to install a pre-commit hook which rejects any
commit on a file which should have svn:needs-lock set but does not,
and inform the user in the error message returned that they need to
set the property and then commit.
If your end-users are using TortoiseSVN, you can try applying the
tsvn:autoprops property to all directories; that would be more of a
convenience than a strict control though.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-07 16:19:52 CEST