[Bitkeeper-users] bk repo's relative checkout location (i.e. like cvs "modules")

[tristan]

Hi,
    I am currently refactoring my build system so that
all the apps and drivers and libraries in the build tree
become separate bk repositories, having the repos split
up with a finer granularity will help in project management
when there are many forks and branches in place.

So lets say I have the following type of structure:

apps/core-app
apps/tools/some-setup-tool
libs/libmoneymanagement
libs/ui/customgtk
libs/ui/operatorui
libs/db/thedblibraries
drvs/soundcard
drvs/money-acceptor
...

We have easily >200 subdirs each responsable for building
a library, an application or a linux device driver, the build
tree must be able to check them all out and build them.

Clearly, checking them all out in a flat directory is
only an invitation to disaster, so I am wondering, how
does one go about storing this meta-data on a repository
so that _the repository knows_ that when you do:

bk clone bk://path/to/operatorui

you intend it to checkout as: 'libs/ui/operatorui' and not 'operatorui'

I did not find this in the documentation...
please let me know your thoughts.

Cheers,
                      -Tristan