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

Re: AuthzSVNAccessFile and collection path syntax

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2005-07-09 10:23:08 CEST

Garret Wilson wrote:

> BTW, what does the AuthzSVNAccessFile do when I have both
> /repos/myresource (text/plain) and /repos/myresource/ (directory), and
> I want to give separate restrictions on them? (Or does Subversion even
> allow a directory with the same name as a file?)

No, Subversion of course does not allow that -- it would translate to
having a directory and file with the same name in your working copy, and
I've not seen a single filesystem yet that allows that.

>> Yes, but [] looks somewhat wrong doesn't it? I wonder if it would
>> even count
>> as a valid config section name.
> The Subversion convention of no trailing slash is also inconsistent
> with its method of designating a repository root directory.
> (Consistency would call for using [repos:] as the root designation.)
> :) My comment was supposed to illustrate the absurdity of such a thing
> and advocate consistency in the /other/ direction---ending slashes on
> all collections, even the root collection.
> Of course, this little AuthzSVNAccessFile syntax thing is a terribly
> tiny thing---I thought I would raise it just to make sure there was an
> awareness of the issue.

I wouldn't mind at all if we _did_ allow trailing slashes in the access
conf file, even if we can't check that they really are collections.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 9 10:24:19 2005

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.