Maybe locking is a bzr thing....

Aaron Bentley aaron.bentley at utoronto.ca
Wed Oct 17 01:51:42 BST 2007


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

Andrew Cowie wrote:
> On Tue, 2007-10-16 at 11:53 -0400, Aaron Bentley wrote:
> 
>> OS locking is only used for working trees,
>> not for branches or repositories.
> 
> How about doing a probe {initially | periodically}

Well, you can't do anything with a dirstate tree unless the filesystem
supports locks, so you'll notice pretty quickly.  No need for periodical
probes.  But it would certainly make sense to ensure that we fail
quickly and gracefully when trying to create a bzrdir containing a
working tree on filesystems that don't support locks.

> to make sure that the
> file system the working tree's directory is in is capable of whatever
> locking you require?
> 
> [I must admit I'm with Alexander on this one, though. Relying on lock
> behaviour working when some of your target environments are not under
> your strict control (ie are remote) seems a bit misguided]

Working trees are never remote, unless you consider NFS/SAMBA "remote".
 In most cases, even if you want your *branch* on an NFS/SAMBA share,
you should keep your working tree on a local disk.  Though some poor
saps have to put up with NFS home directories.

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

iD8DBQFHFVye0F+nu1YWqI0RAjVlAKCH4ZI2/TQoqPrronxcb57z1qvUdACeNV/Q
sToz2IzUdPs+ZnBZKuD7Yh8=
=nAHB
-----END PGP SIGNATURE-----



More information about the bazaar mailing list