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

RE: Newbie: Multiple repositories served by apache

From: Dhananjay Makwana <makwana_at_semandex.net>
Date: 2005-02-18 16:45:55 CET

> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2004@ryandesign.com]
> Sent: Friday, February 18, 2005 4:29 AM
> To: Dhananjay Makwana
> Cc: users@subversion.tigris.org
> Subject: Re: Newbie: Multiple repositories served by apache
>
> On 16.02.2005, at 21:29, Dhananjay Makwana wrote:
>
> > I want to create several repositories under a "/svn" directory on my
> > server.
> >
> > The structure that I want is:
> > /svn/tool/2.0 (repository)
> > /svn/data/2.0 (repository)
> > /svn/dev/2.0 (repository)
> >
> > And later on I want to add more repositories like
> > /svn/tool/2.1 (repository)
> > /svn/data/2.1 (repository)
>
> So you want versions 2.0 and 2.1 of "tool" to be in separate
> repositories? The usual Subversion way would seem to be to have a
> repository for the project, with main development occurring in "trunk"
> and previous development lines maintained (for bug fixes or history) in
> directories in "branches" with tags of specific past releases in
> "tags":
>
> /svn/tool (repository)
> /svn/tool/trunk (main development -- e.g. 2.2 development line)
> /svn/tool/branches (older versions)
> /svn/tool/branches/branch-2.0 (2.0 development line)
> /svn/tool/branches/branch-2.1 (2.1 development line)
> /svn/tool/tags (specific releases)
> /svn/tool/tags/tag-2.0.0 (released version 2.0.0)
> /svn/tool/tags/tag-2.0.1 (released version 2.0.1)
> /svn/tool/tags/tag-2.1.0 (released version 2.1.0)
> etc.
>
> Is there a reason why you're looking for a different approach?

I could still do as you have suggested. The "2.0" directory is actually a
name for our 2.0 architecture. My question is still the same because later
on we might have to add /svn/tools/3.0 as a new architecture repository
(which might be completely different in terms of directory structure of
components)

>
> You can of course also combine multiple projects into a single
> repository. Whether to put everything in one repository or make a
> separate repository per project seems to be something of a matter of
> personal taste.

Since revision numbers are repository-global we would like to keep them
separate for our 2.0 dev and 2.0 demo repositories, for example.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 18 17:15:56 2005

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.