Not following symlinks causes weird bugs

[Aaron Bentley]

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

John Arbash Meinel wrote:
> So basically, on the 'users' directories, they have a symlink over to
> the main repository.

> For now, I've changed their setup to use a BranchReference rather than
> using a real symlink. But this was certainly the source of a lot of
> confusion (for me, and for them).

Yeesh.  As you well know, bound branches are usually a good match here.
 One of the abstraction leaks of our heavyweight-checkout /
lightweight-checkout model is that bound branches are useful by themselves.

I wonder whether we should mention that more often?

> The best I can come up with, is that once BzrDir finds out that there
> *is* a bzrdir at a location, it should then change the transport over to
> a realpath() version of it. And then continue to search for things like
> repositories from the realpath version.

I think that makes sense, but it won't solve the problem on every
transport.  Symlinks are often indistinguishable from normal files.
Perhaps repositories should have a UUID, maybe tied to inode?

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

iD8DBQFF8boE0F+nu1YWqI0RAo4MAJoDd0kuyVX3Z/85Ybo95lJCBjawZwCdEBt+
oEZ29krAo9I3ZlMRgzwobbA=
=batS
-----END PGP SIGNATURE-----