The best way to accomplish that sort of granularity would be with a hook script which would run and examine the committ for deletes and reject it if the user isn't on the list of people who can delete. The infrastructure team where I am working is setting up a set of hook scripts, a database and web font end so we can have directory level security within the repositories.
--Lance Lambert On Feb 5, 2008 2:25 PM, CM Banker <[EMAIL PROTECTED]> wrote: > > > > SVN is a good choice.... I've been using it for almost 3 years... I have > not run across any need to configure it as you describe...but > > > http://svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-6-sect-4.4.1 > > search for "Example 6.3. A sample configuration for mixed > authenticated/anonymous access." > > I think it describes what you need. > > > > > On Feb 5, 2008 1:38 PM, Dustin Puryear <[EMAIL PROTECTED]> wrote: > > > Any Subversion pros here? Someone I know wants to be able to define > > rights such as: > > > > * user A can add/modify but not delete files > > * user B can do anything > > > > I've never even tried this with SVN. Ideas? > > > > -- > > Puryear Information Technology, LLC > > Baton Rouge, LA * 225-706-8414 > > http://www.puryear-it.com > > > > Author, "Best Practices for Managing Linux and UNIX Servers" > > http://www.puryear-it.com/pubs/linux-unix-best-practices > > > > Identity Management, LDAP, and Linux Integration > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > _______________________________________________ > General mailing list > [email protected] > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > _______________________________________________ General mailing list [email protected] http://mail.brlug.net/mailman/listinfo/general_brlug.net
