Re: [PATCH] check name svn special properties

Fabien COELHO wrote:
> The 'one new svn property was added the client was not upgraded and the
> user wants to use it' looks like a rare case, which is easily solved by
> a --force.

Solvable yes, but I don't think it is reasonable. The current
log-message template discussion might require a new property in the svn:
namespace. Once the keywords-as-hash patch gets committed, I'm hoping
to prod things in the direction of inherited properties, which would
almost certainly require a new svn: property. I don't think the new
property case is nearly as rare as you think. And breaking
compatibility between backrev'd client and server (even if there is a
workaround) is a really important consideration.

> The next level is to have a new 'special' property that would list the
> allowed property names, a little bit like svn:ignore, and could be
> fetched by the client.

That would be this issue:

        http://subversion.tigris.org/issues/show_bug.cgi?id=1974

> But it seems as a lot of work for a small problem.

I think you are trying to solve the "problem" in the wrong way. You
should be able to write a pre-commit hook which checks for properties
that do not correspond to the set you wish to support. Until such time
as issue #1974 is resolved, adding validation to the client only is just
asking for trouble, IMHO...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org