Re: svn modules (was Re: Features and release dates)

Ok time to quit being a lurker..

> Unfortunately, symlinks in the repo aren't enough. I believe that Subversion
> will be more multiple-repository-prone than CVS. As an example:
>
> The ASF has one CVS repository, which contains modules for each project:
> httpd-2.0, apr, and apr-util to name a few. However, in SVN land, I believe
> we're have a separate SVN repository for each project. I think the projects
> will want their own directory organization (trunk, branches, tags, whatever)
> and their own (partitioned) set of log messages / revision changes.
>
> As a result, cross-repository "modules" are quite important for SVN. It also
> means that when the ASF switches over to SVN, we can set up a "module" for
> Subversion that references the ASF SVN repositories.

This actually raises a question I've been trying to figure out the answer to for a while now:

I need to control access to the repository at a finer grain than the documentation would indicate is possible. In the example gstein mentions, it's as if I need one set of committers for for httpd-2.0 and another for apr and another for apr-util, with all the sets disjoint. Since SVN is currently lacking the module linking capabilities outlined above, I've placed all my modules in one repository and arranged my directory structure in a globally efficient manner... But the problem remains that anyone who can commit in one directory can commit in all and I have yet to find a combination of LOCATION tags which will let me limit write access to subdirectories in the repository.

(I'm authenticating against OpenLDAP if that matters).

any ideas greatly appreciated.

rvs

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 2 03:43:27 2002