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

Re: Subversion's repositories

From: Tim Hill <drtimhill_at_comcast.net>
Date: 2006-12-04 17:09:17 CET

I would second this ... its usually better to keep everything related
to one project under a single root directory somewhere, rather than
split across functional (dev, qa) boundaries. It does make
permissions slightly more complex to maintain, but overall the gains
are greater imho.

--Tim

On Dec 4, 2006, at 7:28 AM, <Chris.Fouts@qimonda.com>
<Chris.Fouts@qimonda.com> wrote:

> I have a couple of suggestions.
>
> First off, set your repository structure "outside" of Subversion,
> and then "svn import"
> it. With this approach, adding and deleting dirs/files is easier
> since you do NOT have
> to deal with Subversion yet.
>
> Second, there are 1001 different ways to do the dir structure, but
> I suggest the following;
> I'm assuming that priject1, project2, are NOT related
> svn_root
> project1
> trunk
> web
> job
> branches
> dev
> v1
> web
> job
> v2
> web
> job
> qa
> v1
> web
> job
> v2
> web
> job
> tags
> project2
> (same fundamental structure as for project1)
>
> I'm ONLY suggesting the structure because this facilitates
> "logical" branching
> and tagging. For example, for branching
> - You set up your trunk structure first
> - Then you "svn copy" your trunk structure to your branch structure
> > svn mkdir //svn_root/project1/branches/dev
> > svn mkdir //svn_root/project1/branches/qa
> > svn cp //svn_root/project1/trunk //svn_root/project1/branches/
> dev/v1
> > svn cp //svn_root/project1/trunk //svn_root/project1/branches/
> qa/v1
> - Create tags to facilitate merging between trunks and branches, both
> on the trunk and the branches, as soon as you create the branches
> > svn cp //svn_root/project1/trunk //svn_root/project1/tags/
> trunk-to-dev_v1
> > svn cp //svn_root/project1/branches/dev/v1 //svn_root/project1/
> tags/dev_v1-to-trunk
> > (similar for qa branch)
>
> Like I said, this is just "a" way to do it, and not necessarily
> "the" way.
>
> From: T. Nguyen [mailto:ptn_y2k1@yahoo.com]
> Sent: Sunday, December 03, 2006 12:40 AM
> To: users@subversion.tigris.org
> Subject: Subversion's repositories
>
> Hi,
>
> I am setting up a Subversion server. As I read several books and
> searched on the internet, I have not seen any complicated
> repository structure as my workplace requested. Please see the
> following structure:
>
> svn_root
> dev
> project1_root
> project1_web
> project1_web_v1
> trunk
> tags
> branches
> project1_web_v2
> (trunk, tags,
> branches)
> project1_jobs
> project1_jobs_v1
> (trunk, tags,
> branches)
> project1_jobs_v2
> (trunk, tags,
> branches)
> project2_root
> .....
> .......
> .......
> ........
> project3_root
> qa
> ................(same structure as dev)
>
> Here are my questions that I need your helps.
>
> 1. Is it possible to have that kind of structure in Subversion? If
> yes, is it a good or bad structure? And is it easy to maintain
> later? If no, please give me your advise what I should do?
> 2. If it's possible, which level should I use 'svnadmin create' and
> which level should I use 'svn mkdir'?
>
> I am looking forward to receiving your response. Thank you very much.
>
> Regards,
> Tracy
>
>
>
>
>
> Have a burning question? Go to Yahoo! Answers and get answers from
> real people who know.
Received on Mon Dec 4 17:10:07 2006

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