On Jul 16, 2009, at 03:12, 张宇 wrote:
> As our team grows up, we have to divide the big team into small
> ones, and each of the new team has its own configuration manager,
> who will manage the svn authz for his/her own team/project, but
> currently we have one AuthzSVNAccessFile, and the policy in our
> company did not allow the manager to see and modify the authz of
> other team. For example:
>
> Our SVN structure is :
>
> /svn/proj1
> /svn/proj2
> /svn/proj3
>
> Now if we have 2 team: t1 and t2,
>
> So, t1’s manager will see and manage proj1 & proj2, and t2’s
> manager will see and manage proj3, and admin could see and manage
> all of the projects.
>
> The problem is, in our current practice, manage authz requires
> editing an authz file, but if there is only one file, all manager
> will see all projects.
>
> How to setup multiple authz file?
Either split your single repository into multiple repositories - this
will be a pain, but would give you one authz file per repository
Or invent some kind of Makefile or script which glues multiple authz
fragments into a single combined authz file. Give each manager access
to just their authz snippet file, and have a way for the combined
authz file to be regenerated when changes are made to the snippets.
For example, you could host the authz snippets in a repository of
their own (or in a directory in your existing repository) and have a
post-commit hook which uses these to generate the final authz file
after every commit to those files.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371702
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-16 10:39:45 CEST