On Apr 22, 2005, at 11:11 AM, Weintraub, David wrote:
> Actually, even if you specify all possible text file patterns, you
> still have a problem. What if a user does their work on a system where
> you didn't setup the autoproperty for them?
>
> This points to several missing features with Subversion:
>
> 1). No server side configuration. You have to basically set up this
> configuration on all client machines. What if the user overrides this
> configuration? What if the user decides to do work from home on his
> personal computer where you did not setup this client configuration?
> What happens when a machine gets replaced?
This is planned for 1.3. It's a hot item.
>
> 2). Limited power of the svnserve and svnlook commands. Hooks can be
> used to enforce policy, so maybe you'll program a post-commit hook
> that examines a file that gets committed, and automatically sets the
> svn:keyword property if it isn't already set. Oops, the propset and
> propget commands don't work without first creating a working directory
> and checking out that file in that working directory. A hook doesn't
> work.
>
You've got it backwards. You should be using a *pre*-commit hook to
reject any commit which doesn't have properties set correctly. It can
send a nice message back to the use explaining why the commit was
rejected.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 22 18:34:44 2005