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

Re: Re: Inherit the authorization from a trunk to a branch/tag

From: Peter <smile_face_at_21cn.com>
Date: 2007-06-02 14:23:28 CEST

Understood and thanks for your rapidly reply. Waiting the new version the feature added.

Now, we could build some path-rules and create a tools to produce the end-ACL files based on the template ACL file and the root-dir-list in "branchs" and "tags". When create a branchs or tags, run the tools, get the template ACL file, get the root-dir-list of "branchs" or "tags" by svn cmd, cal and produce the end-ACL files, then commit the end-ACL files to the server.

Best Regards

>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
>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

= = = = = = = = = = = = = = = = = = = =

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 2 14:23:33 2007

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.