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

Re: Custom keywords, issue #890

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-09-29 15:28:07 CEST

On 9/28/06, Vlad Skvortsov <vss@73rus.com> wrote:

> This leads to another requirement: autoprops should be customizable on
> per-repository basis. But it seems to me that it's a much simplier
> problem to solve than rolling out iprops or whatever.

The problem (as with most server-side config type questions) is that
you don't necessarily want it to be per-repository, because a
repository may contain many different projects (look at the ASF
subversion repository on svn.apache.org for example) that have wildly
differing standards with regard to things like properties. So you
need to be able to set them on a per-project basis, then you run into
the fact that there's no really well defined "project" in svn, so you
need to be able to set them on an arbitrary directory. Oops, now
you're talking about inherited properties again.

Now, it's not necesarily the crazy complex inherited properties some
people talk about, there are ways to implement it that are simpler (a
proposal was floated around on this list a while back that involved a
special new command that just asks the server "does this property
exist on this directory or any of its parents", which wouldn't be that
bad to implement, but nobody has actually done it yet.

So unfortunately, one way or another you do get back to inherited
properties in some form ;-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 29 15:28:23 2006

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

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