On Oct 22, 2004, at 2:26 PM, David F. Newman wrote:
> On Fri, 2004-10-22 at 13:37, Scott Palmer wrote:
>>
>> I was under the impression that using svn: the only security was
>> read-only vs. read-write for the whole repository, and that you could
>> not apply different security based on the path. So with svn: the
>> 'tags' folder can't be made read-only independently of the trunk and
>> other 'copies'.
>>
>> From the Subversion book:
>> "Notice that svnserve only understands “blanket†access control.
>> A
>> user either has universal read/write access, universal read access,
>> or
>> no access."
>
> The key word here is "svnserve". There are other repository access
> methods.
>
>> So I think my claim still stands.
>>
>
> If you continue reading into the next section you will see that you
> have
> fine grained access control when utilizing an Apache web server for
> repository access. The apache server provides the user authentication
> while the subversion module mod_authz_svn provides the access control
> on
> a per directory basis.
>
Um, that's *MY* point. :)
Subversion doesn't do immutable copies. Apache can be configured to
work around this issue. I simply think that *Subversion* should
support immutable copies as I think it would satisfy many people that
are looking for a kind of tag that Subversion currently doesn't have.
If this was a feature of Subversion and not a hack that can be done
with Apache it *would* work with all repository access methods. I
think it should work the same with all repository access methods.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 21:16:36 2004