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

RE: Auto-prop not working?

From: Weintraub, David <David.Weintraub_at_ilex.com>
Date: 2005-04-22 18:11:26 CEST

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?

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.

3). Limited conversation during a hook. Let's say you finally figure out a
way to add this property to the file via a hook, but maybe there could be
some reason this property shouldn't be set even though the file is a text
file (and maybe even the correct file type).

I remember a case with Sublime which used SCCS as its backend archive.
Someone had a file that used the "date" command which contained the string
"%S%". SCCS expanded that as a keyword which broke the build. What if you
were documenting how keyword expansion worked, and you happened to mention
the string "$Id" in your file, you certainly don't want Subversion expanding
that keyword.

It would be nice to be able to ask the User whether or not keyword expansion
should take place, but the hooks' only means of communication is sending
information to STDERR. You can't have a conversation with the client asking
if this property should be set.

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Friday, April 22, 2005 11:19 AM
To: Michael L Brown
Cc: Subversion mailing list
Subject: Re: Auto-prop not working?

On Apr 22, 2005, at 9:55 AM, Michael L Brown wrote:

> OK, what is one supposed to do?  We can't trust the users to remember
> to set properties on new files they commit, hence the reason for the
> auto-prop setting.  I assumed incorrectly that Subversion would not
> apply keywords to files it considers to be binary.

Be more specific in your patterns, like *.java, *.c, *.txt, etc.

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:10:42 2005

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.