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

Re: tags/branches

From: David Weintraub <qazwart_at_gmail.com>
Date: Thu, 18 Jun 2009 11:31:19 -0400

You can use a single repository, and do this. Take a look at <
http://svnbook.red-bean.com/en/1.5/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir>
and <
http://svnbook.red-bean.com/en/1.5/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.auth.general>.
The first one explains how to setup directory authorizations if you use
Apache. The second one explains how this is done if you use svnserve.
Remember that branches and tags are merely directories.
Most people use this to setup general read and write permissions. That is,
make sure the developers can read and write the entire repository, QA people
can only read the repository, and no one else has access.

You can fine tune write permissions with pre-commit hooks. The standard
Python pre-commit hook and my own Perl pre-commit hooks allow you to specify
who has write and "add-only" permissions on what directories. This allows
you to setup groups, and when you're about to do a release, lock the release
branch except for the two or three people who are working on the release.

My hook script can be found at <
http://files.getdropbox.com/u/433257/hooks.zip>. The Python hook should have
come with Subversion. The Python script is in the Subversion repository over
here: <svnperms.py<http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svnperms.py>>
and the example config is here:
<svnperms.conf.example<http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svnperms.conf.example>>.
The Python script is the standard script that comes with Subversion. My
script is written by me and is unofficial, but does a few things the
standard script doesn't do.

Read the book located at <http://svnbook.com> for more information.

On Thu, Jun 18, 2009 at 10:09 AM, Ramachandran, Vishwanath(IE10) <
Vishwanath.Ramachandran_at_honeywell.com> wrote:

> Thanks David for the reply
>
>
>
> This is my client’s requirement for one of his repository, I have to do it
> no choice [:P]. If it can be done, could you suggest and help me out
>
>
>
> Regards
>
> R.R.Vishwanath
>
> *Desk*: +91 80 26588360 Extn: 44211
>
> *Cell*: +91 9632243577
> ------------------------------
>
> *From:* David Weintraub [mailto:qazwart_at_gmail.com]
> *Sent:* Thursday, June 18, 2009 7:33 PM
> *To:* Ramachandran, Vishwanath(IE10)
> *Cc:* Ryan Schmidt; users_at_subversion.tigris.org
> *Subject:* Re: tags/branches
>
>
>
> On Thu, Jun 18, 2009 at 2:32 AM, Ramachandran, Vishwanath(IE10) <
> Vishwanath.Ramachandran_at_honeywell.com> wrote:
>
> Hi There
>
> I have created a repository and should be configured so that:
> 1. Only administrator(s) can change the branches and tags folder
> 2. A non-administrator (user with read/write access) can have read/write
> access to trunk but not branches and tags
>
> Can this be done?
>
>
>
> There are several ways. One is via the backend server (either Apache or
> svnserve) and the other is a pre-commit hook that allows you to set the
> "write" permissions.
>
>
>
> Some people use a combination of the two because backend permissions are
> harder to set than pre-commit hook permissions. However, the pre-commit hook
> can only set write permissions and not read permissions.
>
>
>
>
> Are you sure you don't want anyone but administrators working on branches? It's strange enough to only allow administrators create all tags, but in most shops, developers must be able to modify a branch. That's what branches are for.
>
>
>
>
> I can understand locking a branch, so only a few users can work on that branch, or to lock a branch once no more work is allowed on that branch, but locking developers out all the time doesn't make much sense.
>
>
> --
> David Weintraub
> qazwart_at_gmail.com
>

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2363240
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-18 17:32:20 CEST

This is an archived mail posted to the Subversion Users mailing list.