Garrett Rooney wrote:
> 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 ;-)
I still don't see a need for inherited properties here though. Given
that pre-commit hook ensures keywords are properly set up, this boils
down to a configuration problem. And why not use something as simple as:
[autoprops-set-freebsd]
FreeBSD = %r
[repository-freebsd]
# Any of these URLs match.
url = https://svn.freebsd.org/
url = svn://svn-freebsd.lan/
# ... in conjunction with any of these paths within repository.
path = /main
path = /another-subtree/project-a
# Use this autoprops setting for the match.
autoprops = autoprops-set-freebsd
The problem here is that pre-commit hook and clients' autoprops settings
need to be kept in sync. The proper way to solve this for a long term
seems to be to configure that on server side and let clients discover
the settings.
However, in the meanwhile it is possible to solve the problem at hand
without both iprops and "server-side autoprops".
--
Vlad Skvortsov, vss_at_73rus.com, http://vss.73rus.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 2 22:23:44 2006