[ANN] bzr-colo 0.0.1: colocated branches using present technology

[Alexander Belchenko]

Neil Martinsen-Burrell пишет:
> On 2010-01-11 14:37 , Alexander Belchenko wrote:
>> Neil Martinsen-Burrell пишет:
>>> On 2010-01-11 03:06 , Alexander Belchenko wrote:
>>>> Neil Martinsen-Burrell пишет:
>>>>> This plugin does not add any new formats or objects to Bazaar, it
>>>>> simply
>>>>> provides convenience commands for working with a certain *convention*
>>>>> for branch storage. This plugin provides the following commands
>>>>>
>>>>> * colo-init
>>>>> * colo-branch
>>>>> * colo-branches
>>>>> * colo-fetch
>>>>> * colo-clone
>>>>> * colo-prune
>>>>> * colo-clean
>>>>> * colo-ify
>>>>
>>>> There is one more command required: to adjust the checkout location if
>>>> user move the colo branch on the filesystem. Because bzr uses absolute
>>>> path to master branch it's very necessary.
>>>>
>>>> Also see https://bugs.launchpad.net/bugs/330086
>>>
>>> It's mentioned in the Tutorial under Limitations. I suggest using
>>> ``bzr switch --force`` there. From the root of the checkout, you can
>>> use relative paths ``bzr switch --force ./.bzr/branches/trunk``.
>>
>> It seems you and Aaron missed my point.
>>
>> What if I want just update the lightweight checkout reference without
>> switch to trunk?
> 
> You can update the lightweight checkout reference to any branch you want 
> inside .bzr/branches

I know, thanks.

> 
>> And my current branch is not trunk?
> 
> Just ``bzr switch --force .bzr/branches/other-branch``.

I know this too, thanks.

>> And I don't remember which branch is current?
>  > And I have ten branches inside .bzr/branches?
>  >
>  > How can I know what I should switch --force?
> 
> This is trickier.  Then, we need to infer from the current (incorrect) 
> content of .bzr/branch/location what the current branch name should be. 
>  (Hmm. This shouldn't be too hard since .bzr/branches will most likely 
> only occur once in the path inside .bzr/branch/location.  Then we can 
> just figure out the mapping between . and the rest of the path there.) 
> Could you file a bug on bzr-colo about this?  It probably does need a 
> new command ``colo-fixup`` that uses knowledge of the particular 
> structure at work her to reconnect things.

Finally we reached the core of the problem. I'll file a bug.
Yesterday I've tried to write some patch to address this problem, but it becomes a bit tricky 
because there is no straightforward way in bzrlib to manipulate with branch references.