hi...
i'm strongly considering using svn.. and i'd like to get some
opinions/comments...
i'm considering an environment, where each function in an app will be
completely separate. i want to restrict the users working on the app to the
given function(s) that they have been assigned. as i understand svn, i
can/should be able to use apache/svn/mod_dav_svn and create a kind of
directory level access process, that will allow me to have users log into
svn, and restrict the dirs that the user has access to.
so far, so good.
the issue that i'm looking at has to do with the underlying working copies.
if i create the user access information on the server, the user then uses a
svn client to access the repository. on the client side, the user would
create a working dir/copy area. the user would then be able to
checkout/modify the files from the dirs that he has access to. this process
should allow the user to be able to access files from multiple dirs, and to
be able to check the files back in without accessing files in other areas.
have i missed anything...
i envision 400-500 separate dirs for the various apps. i'm also going to
have to periodically copy the different versions (once an app works!) into a
separate 'tag' dir.
comments/feedback/thoughts welcomed...
thanks...
-bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 6 03:00:23 2004