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

Re: dav_svn and directory hierarchie

From: Yves Dorfsman <yves_at_zioup.com>
Date: Thu, 22 Jan 2009 07:50:31 -0700

Tony Butt wrote:
>> I cannot believe nobody run into this problem before. It is typical of CVS
>> servers to have multiple "modules" under one "repository", and multilple
>> "repositories" under one "root". A "CVS module" correspond to a subversion
>> repository. I cannot believe that people have hundreds of svn repositories
>> into one directory ?
>> How do you address this ?
> You address it by not having one module or project be one subversion
> repository. Effectively you could make the top level directories of four
> subversion repository be equivalent to CVS modules, or you can impose
> any other tree structure you wish.
> It is trivial to divide a repository into separate projects, and manage
> multiple projects in a single repository. The most difficult part we
> found was finding a workable directory structure standard, getting 20
> software engineers to agree on it, and then enforcing it.

But then, doesn't this mean that any change in any of the project changes
the version for the whole repository ?

So if I have four projects inside one repository (and in our case, it is
more like 60 !), no project is made to one project for a year, while the
other projects are very active, the one project is now a revision N + 40,
while no change whatsoever has been made to it ?

Or am I confused ?

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-22 15:51:25 CET

This is an archived mail posted to the Subversion Users mailing list.

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