repository structuring question

I'm very new to bitkeeper and am having trouble figuring out how to
structure our bk repository and could use some guidance. We have a generic
model checking code base, cmc, that is used by a variety of projects.
These projects typically involve running cmc on another large source base,
like the linux kernel. When we are checking a codebase we typically need
to both improve cmc and edit the code base being checked. These changes
sometimes depend on each other.

What we would like to do is have a repository for each checked-code-base, 
cmc pair and be able to pull/push changes from separate repositories for 
each of cmc and the checked code while maintaining some form of history 
for the pair as they evolve together.

For example, if I'm checking linux-2.4.x and linux-2.6.x with cmc I would 
like to have three repositories:

cmc		- stable evolution of the model checker
linux-2.4	- the latest 2.4 kernel source and our local changes 
linux-2.6	- the latest 2.6 kernel source and our local changes

I would then like to have two meta or packaging repositories cmc-linux-2.4 
and cmc-linux-2.6 which each contain cmc and linux source and where I can 
make changes related to checking linux-2.{4,6}.x with cmc. Thus each meta 
repository would serve to group changes related to working on a task with 
two tools: cmc and linux. I would like to be able to push improvements in 
cmc developed in cmc-linux-2.4 to the main cmc repository and kerenl 
tweaks to our local copy of linux-2.4.

What's the best way to have a workflow like this with bk? I did a brief
search of the list archives and couldn't find anything other than vague
mentions of perl hackery. If my question has been answered before please
point me to a URL.

TIA


Paul Twohey
twohey@cs

_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.