steveking wrote:
> Wouldn't this feature also cover repository settings? I mean something
> like a conf-file stored in the repository which then clients would fetch
> with every update (like the UUID) and would be stored in the wc.
> Only it wouldn't be a config file but all configs would be stored as
> props in root. So this could also cover issue 1974:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1974
Looking over 1974, I don't think that what is being discussed there is
likely to fit into the entries file itself (which is all I'm talking
about). I suspect for the limited set of repository settings that would
be supported (taking heed of Greg Hudson's comment) would require a new
file (or files) in the administrative directory to store those
overwrites (like .svn/autoprops and .svn/mime-types). Whether these get
fetched with every update, or only when changed, is a different
question. Indeed, I suspect uuid is transferred everytime more as a
failsafe against MITM attacks (since it doesn't actually change).
Although I've also considered this sort of functionality as being very
doable with inherited properties (another feature I'd like to work on).
With that in place, the repository could be mined with all sorts of
properties which the individual WC files would simply inherit. My
current thinking is that inherited properties would live in the
directory entry containing the files, and that the server would be
resposible for sending that out for each directory during checkout.
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
Received on Mon Jan 3 17:18:06 2005