There is an alternate to using auto-props which relies on each user to
install and maintain their auto-props configuration. Past experience
shows that this type of thing doesn't work well. The trick is to
install a client on the server box and have your commit hooks perform
the desired operations on it. In our case, the post-commit hook updates
the server-side-client upon every commit and then it tests the file(s)
to see if the needs-lock property exists. If not and they are desired,
they are added. The only downside is that these files will need
updating in the users working copy before they can re-commit them. Once
Bug #443 is fixed, an update reminder can be displayed.
-----Original Message-----
From: Sven Kirchner [mailto:Sven.Kirchner@innomea.com]
Sent: Wednesday, January 11, 2006 5:24 AM
To: users@tortoisesvn.tigris.org
Subject: Setting auto-props for svn-needslock on server or client?
Hello,
I want to use the SVN auto-props feature to automatically set the
svn-needslock property for non-mergeable files. I have read the docs but
I am still not 100% sure how to exactly use the auto-props feature for
my goal.
I am using TSVN accessing a repository via svnserve, "svn://".
Let's say I want to have every .bin file added to the repository have
the svn-needslock property set. Do I have to set the feature in all TSVN
clients' config file? (which would I'd try to avoid) Or can I set the
option somewhere on the server/repository side? (which I'd prefer)
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Jan 11 19:54:23 2006