Performance of bzr update for lightweight checkout
Eli Zaretskii
eliz at gnu.org
Sat Feb 5 09:27:36 UTC 2011
> Date: Fri, 4 Feb 2011 22:11:44 +0100
> From: Ulrich Mueller <ulm at gentoo.org>
> Cc: bazaar at lists.canonical.com
>
> So, would the following be a more appropriate scheme for us?
> 1) initial branch with "bzr branch --no-tree" (maybe preceded by
> "bzr init-repo --no-trees" if there are live ebuilds for several
> branches of the same project?)
> 2) temporary checkout to the local build directory with
> "bzr checkout --lightweight" (which will be deleted when the
> package has been installed)
> 3) later updates of the branch with "bzr pull"
If you only use this branch for building the upstream versions,
without any local changes, then why not just "bzr branch --bind"
(which will include the working tree)? You would then build out of
that tree, and sync with upstream with "bzr update". Am I missing
something?
More information about the bazaar
mailing list