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

Re: Installing suberversion to allow versioning on multiple projects

From: Andreas Pakulat <apaku_at_gmx.de>
Date: 2006-06-13 00:16:57 CEST

On 12.06.06 16:33:17, Matthew Kidd wrote:
> I was tasked with the conversion of our versioning system from CVS to subversion. So far things are going smoothly but I am getting confused with the aspect of keeping the versioning separate amongst our several projects and avoid the "synchronous" versioning that would occur if all the projects were in one repository.

Among subversion users it's common sense (AFAIK) that you shouldn't care
wether your projects "share" revision numbers or not. Anyway,...

> The place I am getting confused is right after the "svnadmin create /path/to/repos" that creates the central repository. I don't want that. I want separate repositories for each project that we have resulting in a directory structure like below:
> projectA
> /trunk
> /branches
> /tags
> projectB
> /trunk
> /branches
> /tags
> projectC
> /trunk
> /branches
> /tags
> .....etc
> Do I need to create central repositories for each project?

Yes, you need to do exactly that.

> If so how do the directories created via the "svnadmin create" factor in to the directory structure I want above?

Not sure if this is what you mean, but you would to something like

svnadmin create /path/to/where/repos/are/projectA
svnadmin create /path/to/where/repos/are/projectB
svnadmin create /path/to/where/repos/are/projectC


You get along very well with everyone except animals and people.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 00:18:22 2006

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.