What is a safe way of backing up a shared bzr repository

Aaron Bentley aaron.bentley at utoronto.ca
Mon Nov 19 20:46:46 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Fangohr wrote:

> I agree with Vincent: bzr should really provide a simple script (and a
> short section in the manual) that provides exactly this
> functionality. Ideally, this would create a (consistent) copy of the
> repository in a different place.

So it seems we have several options here:

First, delivery:
1. command
2. script

It's rare for us to provide scripts when we can provide commands
instead.  I'm not terribly keen on introducing new commands, as some
people use the length of the command list as a metric for deciding how
easy a tool is to use.

Next, scope:

Option 1: lock-and-foo
This is basically what my script provided.  It allows any arbitrary
command to be run with a locked repository.

Option 2: lock-and-copy
This folds the copying into part of the script, e.g. with shutil.copytree

Option 3: lock-and-fetch
This uses the appropriate bzr facilities such as fetch to produce (or
update) a mirror of the repository.  This has the advantage of
potentially working over remote transports, including the smart server.
 But the remote transport must be listable in order for Bazaar to
discover branches.  This option is typically much slower than the others.

Further thoughts?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQfY20F+nu1YWqI0RAjjtAJ0cGxiwMKaYrZMQc7XSgSC1LAGdgQCeOT2H
a2EF2hhimLwN6ZXADvecYtI=
=8TMk
-----END PGP SIGNATURE-----



More information about the bazaar mailing list