Demonstration Help.

[Colin D Bennett]

On Fri, 20 Feb 2009 09:30:25 -0800
Eric Berry <elberry at gmail.com> wrote:

> Thanks so much everyone for all the help.
> 
> I'm still learning the terminology and the differences between BZR and SVN.
> I think the simplest thing will be to just go through and actually try to
> implement the scenarios I want to demonstrate.
> 
> I do have a question regarding the shared repositories though - in regards
> to shared repositories on a "server", and those hosted locally.
> 
> On my server I've set up several projects each of which consists of it's own
> repository - allowing many branches of the same project to share the
> repository. If I branch off of the remote project's branches locally, can I
> save space by putting those branches into a shared repo locally?
> 
> Eg. On the server I have this:
> [quote desc="plain vanilla directories on the host"]
> ftp://[host]/ProjectA
> ftp://[host]/ProjectB
> ftp://[host]/ProjectC
> [/quote]
> 
> For which I have run these commands:
> [code]
> bzr init-repo --no-trees ftp://[host]/ProjectA
> bzr init-repo --no-trees ftp://[host]/ProjectB
> ...
> [/code]
> 
> Then created main branches for each:
> [code]
> bzr init ftp://[host]/ProjectA/main
> bzr init ftp://[host]/ProjectB/main
> ...
> [/code]
> 
> Now I branch off of the main branches locally using, "bzr branch
> ftp://[host]/ProjectA/main
> ProjectA". I know, I should keep a clean branch of the main branch locally -
> working through it slowly :)
> 
> If I had created a local repository first, would I still gain the benefits
> of the shared repo?
> 
> Eg.
> [code current_dir="~/development/projects"]
> bzr init-repo .
> bzr branch ftp://[host]/ProjectA/main ProjectA
> bzr branch ftp://[host]/ProjectB/main ProjectB
> bzr branch ftp://[host]/ProjectC/main ProjectC*
> *[/code]

Yes, when Bazaar creates the local branch copy of ProjectA/main,
ProjectB/main, etc., it will notice that the local target directory is
below a shared repository directory in the filesystem hierarchy, so it
will store all the actual revision data in the shared repo, making the
actual branch data very small (on the order of 100 KiB), plus the
working tree since you implicitly specified to create working trees as
well.

Also, in the case above, where you have 3 apparently "unrelated" (from
the perspective of Bazaar history, at least) branches being stored in a
single shared repository, that is fine and can mean easier
administration for you -- the shared repo really acts fairly
transparently.

Regards,
Colin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090220/eafb4a94/attachment.pgp