atom feed61 messages in com.ubuntu.lists.ubuntu-distributed-develRe: Recipes vs. Looms vs. pipelines
FromSent OnAttachments
32 earlier messages
Aaron BentleyDec 17, 2009 8:03 am 
John Arbash MeinelDec 17, 2009 8:27 am 
Barry WarsawDec 17, 2009 8:53 am 
Barry WarsawDec 17, 2009 8:53 am 
Barry WarsawDec 17, 2009 8:56 am 
Barry WarsawDec 17, 2009 9:01 am 
Barry WarsawDec 17, 2009 9:03 am 
Vincent LadeuilDec 17, 2009 9:17 am 
Aaron BentleyDec 17, 2009 9:42 am 
Vincent LadeuilDec 17, 2009 10:21 am 
Aaron BentleyDec 17, 2009 10:26 am 
John Arbash MeinelDec 17, 2009 12:27 pm.png
Vincent LadeuilDec 18, 2009 12:31 am 
Barry WarsawDec 18, 2009 2:06 am 
Barry WarsawDec 18, 2009 2:16 am 
John Arbash MeinelDec 18, 2009 7:06 am 
Aaron BentleyDec 18, 2009 7:20 am 
Aaron BentleyDec 18, 2009 7:42 am 
John Arbash MeinelDec 18, 2009 7:46 am 
Vincent LadeuilDec 18, 2009 8:57 am 
Vincent LadeuilDec 18, 2009 9:28 am 
John Arbash MeinelDec 18, 2009 9:31 am 
Vincent LadeuilDec 18, 2009 1:41 pm 
Barry WarsawJan 4, 2010 8:14 am 
Aaron BentleyJan 4, 2010 9:09 am 
Robert CollinsJan 4, 2010 3:33 pm 
Dmitrijs LedkovsJan 4, 2010 3:49 pm 
John Arbash MeinelJan 5, 2010 8:30 am 
Robert CollinsJan 5, 2010 1:09 pm 
Subject:Re: Recipes vs. Looms vs. pipelines
From:Aaron Bentley (aar@canonical.com)
Date:Jan 4, 2010 9:09:27 am
List:com.ubuntu.lists.ubuntu-distributed-devel

Barry Warsaw wrote:

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.

That is right. If you find any problems with this, please report them as bugs.

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

I saw that, and I'm 95% certain I'll land it as-is. It's possible I'll add an option to restore the previous behaviour. My original motivation for using a location outside the .bzr was to avoid too much "magic". I was on a "pipes are just branches" kick.

I should mention that, as a launchpad developer, you probably have a bunch of configuration in ~/.bazaar/locations.conf that uses the "appendpath" configuration policy to set your public, submit, pull and push locations. Have a look with "bzr info" to see if any of those locations have gone haywire.

(https://bugs.launchpad.net/bzr-pipeline/+bug/416962 is related to the appendpath issue.)

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.

I think that most of the time, if there's a lightweight checkout, the user has already decided to put their branches somewhere else. So I think there may not be any demand for this.

Aaron