User question : does bzr have an equivalent to "tla archive-mirror"?

[David Allouche]

On Sun, 2005-12-11 at 13:40 +1100, Erik de Castro Lopo wrote:
> I brought this up on #bzr and ddaa had a number of suggestions for
> getting close to the Arch functionality. (Hopefully he can correct
> me if I get anything wrong here).
> 
>   0) Keep all the projects under Bzr control in a single directory
>      and rsync. This is suboptimal because unless I am extremely
>      meticulous about keeping the .rsyncignore files up to date, I 
>      end up rsyncing all sorts of junk which I don't need.
> 
>   1) Keep a separate clean copy of each branch that only contains 
>      files under revision control and rsync that.

What I suggested here was a "repository by policy": a "repo" directory
that contains branches that are only created and modified with "bzr
push". 

Since bzr push does not update the checkout (only the branch and the
store) the repo will not contain any source file, even less build cruft.

Then you can rsync the repo over without needing any rsync ignore rule.

The only gotcha is that you have to be vaguely disciplined about keeping
your repo clean: not creating branches there with "bzr branch" or by
copying checkouts.

I think this is the more efficient solution given bzr current
limitations.

>   2) Keep all Bzr projects in a single directory and write a script
>      which does a "bzr push" for each directory in the Bzr directory.

As John pointed out in his reply you could easily extend or modify his
update-mirrors plugin to push.

> Ddaa, does that about cover the possibilities? Does anyone else have
> any suggestsions? Is this a feature that might go into bzr at some
> point in the future?

As James noted, repositories will be supported (as an optional feature)
by bzr in the future. That should make your use case much easier.

At the moment, I think it would be possible to make the "repository by
policy" more transparent by using bound branches (I believe John Meinel
has a branch with that feature somewhere), so commits on a working tree
would update the "repository" automatically.

What bound branches + "repository by policy" looses compared to proper
repositories is the space saving by not duplicating common branch and
store data.
-- 
                                                            -- ddaa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051212/f05cbed1/attachment.pgp