Comment 6 for bug 135234

> Have you considered the case where the checkout is moved, but the bzr branch stays in the same place?

I think the file level operations should work without hick-ups:

  $  mv repo.bzr /other/location/in/disk

This way tarring up files and directories. moving them around, works like with any other directory.

I think it is reasonable to assume that the way user writes the URL to clone is preserver "AS IS". If he wants absolute paths, he uses absolute paths in the URL.

  $ bzr clone ../tools.bzr tools # relative
  $bzr clone $(pwd)/tools.bzr tools # absolute

This is especially important when making branches under a share repository where relative paths are used 99.9% of the time. Without the relative paths, the shared repository ROOT is immovable (if I understand correct) with mv(1) to another location on disk (disk full, reorganization, etc).

E.g. Git stores clone information as user types it in .git/config