Brass Tilde wrote:
> > We've got most of our projects in the one repository. The only reason
> > we've got multiple repositories is for vastly different areas - ie we
> > have a repository for software development, and another that houses our
> > server configuration files (eg the contents of /etc)
>
> > Other than that I see no compelling reason why we would want to create
> > seperate repositories for different projects.
>
> Each of our repositories will be read/write for the group that's responsible
> for that major product group, and read-only for everyone else. Our network
> admin wants to set up the access rights to the various repositories using
> groups under Windows and he's of the opinion that will be easier than trying
> to manage it in Apache.
I takes about 50 lines of perl and apache's mod_perl to pull in
permissions from an LDAP server (like your favourite Windows domain
controller for instance).
This is orthogonal to one-project-per-repository or not.
Andre'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 26 17:44:57 2005