[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: auto-props on the server?

From: David Weintraub <qazwart_at_gmail.com>
Date: Fri, 22 Aug 2008 11:38:00 -0400

On Fri, Aug 22, 2008 at 3:17 AM, Klaus Umbach <treibholz_at_gmail.com> wrote:
> Hi,
> Is it somehow possible, to set auto-props on the server-side?

This is one of my complaints, but I can see why it isn't done. For
this to work, the client would have to talk with the server whenever
it did a "svn add". Plus, you'd have to setup a whole way of
conversing with the server.

The best you can do is create a configuration file with the
autoproperties already configured. Then, run a pre-commit script and
reject any commits that don't have the correct properties. I have a
Perl hook I use that can do pre-commit property checks. I don't know
if the default Python script does.

As part of the pre-commit hook, have it print out to STDERR when a
commit fails due to a missing property the location of the
configuration file and directions on how to use it. After no more than
two bad commits, developers will download and install the
configuration file.

Of course the other issue is that the autoproperties file is for ALL
repositories which could be a problem. Imagine a Windows based
repository where you want svn:eol-style be "CRLF" and a Unix based
repository where you want "svn:eol-style" to be "LF". It is impossible
to setup that type of autoproperties configuration.

David Weintraub
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-22 17:38:27 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.