The two subversion servers (apache and svnserve) have the abliity to
do access control on paths in the repository, and the book discusses
this. When you create a branch or tag, you create a new path, and
thus the access control on that new path is entirely determined by
whether your existing authorization rules happen to cover that path or
not.
The feature you're asking for -- where the ACLs are inherently
"attached" to files and directories -- is only possible by adding ACLs
within the repository itself. In other words, we'd have to move the
authorization feature from "something enforced by the server" to
"something inherent in the repository data". That's on our wishlist
as something that would be nice to have someday, but it's not on any
roadmap just yet. It would likely be slated into a subversion 2.0
repository-redesign (along with several other features.)
For now, all you can do is add more rules to your access control files
to cover new branches and tags.
On 6/2/07, Peter <smile_face@21cn.com> wrote:
> Hi all,
>
> Is there any method to inherit the authorization when "svn copy" done.
>
> The following is the structure of my module in the repos:
>
> .../cal/trunk
> .../cal/branchs
> .../cal/tags
> .../cal/trunk/util
> .../cal/trunk/main
>
> When I copy the trunk to tags by "svn copy .../cal/trunk .../cal/tags/t-1.0.0", I found the authorization about ".../cal/trunk/util" and ".../cal/trunk/main" did not be inherited by ".../cal/tags/t-1.0.0/util" and ".../cal/tags/t-1.0.0/main".
>
> And I read the book of subversion, cannot found any description abort that. But I regard that the svn server can track the "svn copy", so it might copy the authorization from the source to destination when do the "svn copy", in the abstract.
>
> Best Regards
> Perter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 5 21:37:04 2007