Single-user operations getting locked in a shared repository

John Arbash Meinel john at arbash-meinel.com
Thu Oct 18 16:00:48 BST 2007


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

Vincent Vertigo wrote:
> Thanks Aaron, I get the idea.
> 
> I am currently evaluation Bazaar as a replacement for another VCS we use
> in the company; the examples I gave may not reflect the real situation:
> multiple developers working on the same machine.
> Therefore, I was thinking of each developer creating a checkout of a
> shared branch, and because everyone is working on the same machine,
> requiring only one shared repository. Does that seem less 'fairly strange'?
> 
> Anyway, thanks for your explanations, I'll work around that.
> 
> Regards,
> Vincent.

So with everyone working on the same machine, and working on the same branch,
you probably want lightweight checkouts.
That will let them put the checkout wherever suits them best (in their home
dir) rather than forcing them to keep it underneath the shared repository.

So *I* would go with something like:

bzr init-repo --no-trees /srv/project
bzr init /srv/project/trunk
cd ~
mkdir work
cd work
bzr checkout --lightweight /srv/project/trunk project


Now you have a directory ~/work/project which you can commit/update/etc it. And
it will stay in sync with /srv/project/trunk.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHF3UgJdeBCYSNAAMRAo2mAJwJVRQ3JYveoK8hUHnf0shYR3MCCQCgjQGc
8SU5aCCzjUPRR8dbh/FcC8k=
=snX+
-----END PGP SIGNATURE-----



More information about the bazaar mailing list