Recipes vs. Looms vs. pipelines

Barry Warsaw barry at canonical.com
Mon Jan 4 16:15:06 GMT 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Resurrecting a thread from a few weeks ago...

On Dec 17, 2009, at 01:26 PM, Aaron Bentley wrote:

>Barry Warsaw wrote:
>> I like this because there are
>> no extra directories to worry about, and I can delete the loom
>> directory in one rm-rf and be completely done with it.
>
>This is actually co-location of trees with their branches.  You can
>accomplish this with lightweight checkouts by putting the branch inside
>the .bzr directory of the branch.
>
>$ bzr init foo
>Created a standalone tree (format: 2a)
>
>$ bzr checkout foo bar
>$ mkdir bar/.bzr/branches
>$ mv foo bar/.bzr/branches/
>$ cd bar
>$ bzr switch --force .bzr/branches/foo
>Tree is up to date at revision 0.
>Switched to branch: /home/abentley/sandbox/bar/.bzr/branches/foo/
>
>Obviously, this is more steps than it should be, but it would be easy to
>turn into a reconfigure operation.

Correct me if I'm wrong, but reconfigure-pipeline is actually pretty close to
what I want, I think.  'bzr reconfigure-pipeline' will create a ./pipes
directory in the current working tree, and all new pipes will go there.  If
this was named .bzr/pipes instead I think that would be perfect.

I did a quick and dirty hack which seems to DTRT.

https://bugs.edge.launchpad.net/bzr-pipeline/+bug/503006
https://code.edge.launchpad.net/~barry/bzr-pipeline/dotfile

It does mean that instead of doing a lightweight checkout to start with, I
would use a straight up 'bzr branch foo bar' then reconfigure.  I could live
with that.  Maybe a better name for that would be 'init-pipes'.  I'll just
add that as the sixth essential pipeline alias. :)

Hacking reconfigure to set up .bzr/pipes when run in a lightweight checkout
might be a good idea too, but I don't think I'll tackle that one.

- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJLQhQKAAoJEBJutWOnSwa/w88QALxj61jvNuYI18lwRh86uked
u/cSpGWFd7cd1lffmw8loFim8tfjUUBLHglMmmlyrIsl/6RCPGk7OhF6vymWWpSZ
M1nQEJeUTK4XVzuwPynD5yq0YTNsH45YbNo+WZmAMghC9jFwFq4LM8vhVWf+uULa
hwcCYwBYGQYncUTah9kllyjqpATX7Xk4H6tUy3H7EbTzFHoT6ma0WS4WOy62OPrr
cqT4qBj0gFeWpcxq12T0Vhgzgvg0vvyh93YrM+A4CKB2jr754GhR+5f0H7oUp9ud
67w+RDzIQkyyWKWbHpyxDWe+VZY3O2jJm4/q431jiWKowEqCjQMxnxbBpq8xJVwE
3jgm0uEK4Vty+aBvDJKZPHOHJqvf1vw+nulps2qnzEzEWkjvKYL1gb2cJ+zcIPaV
5SsmuCsRG7x1UWUBDEbvNW8KuYMeCDqPVLEM3FssJuhu19FyF06FTG/QMDLM49GE
JfwCXIvY1Dbujf3j7SHDMGCkOs3AVaBd0mx4UvLXtairklWpq0UPDWIo4ApxeOSm
l2TDhpjLl4HbcZSAtcVeI0ezpd/VWK543BcfHs/zDYtgoY6vJQSCog1yuz7+Nf5M
S/jqS1kjn1J+T2VApbuXxCR3FuftBHr5VEazC1LfIGVzSL/oyrYxsp8QChh2OnvI
SV7HWknL1w2PBD5JSMcQ
=Hz3A
-----END PGP SIGNATURE-----


More information about the ubuntu-distributed-devel mailing list