Bazaar

Help with setting up an advanced shared repository

Asked by William Chambers

I'm trying to setup a somewhat-complex shared repository. I've used bzr in the past but I've never been the one who decides on the repository layout or had to do that before so I'm not quite sure what's standard. I'm looking at using a format such as this. (Slightly modified with a 'branches' directory from http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/shared_repository_layouts.html )

project1/
 +- trunk/
 +- branches/
     +- johndoe/
         +- feature1/
             +- broken/
         +- feature2/

But I'm not actually sure how to go about doing this. Are the branches and johndoe directory's just normal folders? And how/why would I go about using --no-tree? And for that matter, is this layout overly confusing/idiotic? >.>

Thanks for any help you can give. :)

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Wouter van Heyst
Solved:
Last query:
Last reply:
Revision history for this message
Best Wouter van Heyst (larstiq) said : 		#1

They are indeed normal folders. If project1/ is a shared repository, branches below it will use that as their repository.
If this is a central repository you're setting up for sharing branches, then working trees will only be a waste of space as no one will use them (ie, you want --no-trees there).

The layout is fine, perhaps overkill for a small project. You can start with just having project1/trunk/ and expand later when the need arises.

Revision history for this message
William Chambers (bioselement) said : 		#2

Thanks Wouter van Heyst, that solved my question.