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

tortoise/svn question

From: bruce <bedouglas_at_earthlink.net>
Date: 2006-06-10 01:56:24 CEST


i can setup a svn repository to allow users to access the underlying
folders/files. i can allow users to access the repository using tortoiseSVN.

a possible structure is:


i'm trying to determine which setup makes sense...

my goal is to allow certain users to be assigned certain roles
(dev/rev/test). this allows me to create a simple/basic kind of workflow for
the file/script. only users with the given role would have the right to
access/modify/check (in/out) the file.

if i use separate folders, with each subfolder maching the role, it gets to
be easy. i can simply copy the file to the next folder, and restrict the
access rights to the folder to the given user in the access file. this model
would work with tortoiseSVN fairly easily.

if i use only one file, then i'm not sure how much underlying/behind the
scenes manipulation of the user access file i'd have to do as a user
modifies the script file. if someone with a dev role modified the file, i'd
have to then go into the access file, and change the access rights to remove
the person with the dev rights, and add the person with the rev rights...

is there another possible way that i'm missing...



To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Jun 10 01:54:09 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.