Comment 8 for bug 760649

Jelmer Vernooij пишет:
> On Thu, 2011-04-14 at 13:39 +0000, Alexander Belchenko wrote:
>> Jelmer Vernooij пишет:
>>> On Thu, 2011-04-14 at 13:10 +0000, Alexander Belchenko wrote:
>>>> Jelmer Vernooij пишет:
>>>>> bzr-externals currently uses a file in the versioned tree to find
>>>>> information about externals.
>>>>>
>>>>> It would be neat if it supported an external versioned file to look up
>>>>> the externals, e.g. a file in .bzr/externals/.
>>>> What do you mean by "external versioned file"?
>>> A knit or something like that which has a history parallel to the
>>> repository revision history.
>> Do you mean something like loom tracks its history?
> I think that's different. Looms are a custom branch format, what I'm
> talking about is independent of the branch format.

I don't think it's too different. IIRC loom keeps its own history as
hidden (dead) head in the same bzr repository.

IIUC your intent you want to have parallel history for .externals
settings in the same repo, doesn't you? Or maybe you have in mind
separate branch with its own history in .bzr/externals?

I've tried to keep the history of the project in separate directory in
early days of scmproj plugin. It was big failure point for me.

>> I wonder how it
>> should work on branch/pull/push?
> It would need some sort of fancy hook to properly pull/push/branch
> between bzr branches.

That "fancy" part is most difficult part, IMO. Do you plan to implement
it yourself as core bzr dev?

--
All the dude wanted was his rug back