OT: Re: [scponly] subversion support

[Dimitri Papadopoulos-Orfanos]

Hi,

> So in the svn+ssh: case it should be possible to enforce access to the 
> files based on user, groups, and file permissions:
> http://svnbook.red-bean.com/en/1.1/ch06s03.html#svn-ch-6-sect-3.4
> Could you please elaborate on this:
>     Because of the BDB and FSFS structure, I can't give them just
>     filesystem access to a single path within that tree no matter
>     how many ACE's and groups I create.

OK, I think this is what I'm misunderstanding.

We have been using Perforce for years. The Perforce repository stores 
files as files. The tree you have on your working copy is also found on 
the Perforce server's file system. I thought one could control the 
server's tree using the server's filesystem access control.

But it looks Subversion stores files in a single file instead of 
replicating the tree in the working copy in the server's filesystem. 
Which means you're still left with subversion's blanket access control. 
Is that correct?

If so I understand why you're using 'https:' instead. But again, why not 
directly use the HTTPS protocol and use SSH authentication instead?

Dimitri Papadopoulos