Disconnect between module versioning and module project versioning?

[Chris Hillery]

A module in Zorba can be versioned. It is possible for a single build to contain multiple versions of the same module.

The unit of non-core modules, however, is a module project. This is a single branch in bazaar, equating to a single directory in a build. These module projects can be versioned, both in bazaar as well as being tagged with release versions. It isn't possible to build Zorba with more than one version of a module project (because the PROJECT() declaration in CMake won't be unique). It is possible for a single module project to contain multiple versions of the same module, not to mention multiple different modules.

Right now the only mechanism for declaring dependency relationships between non-core modules is at the module project level. This means it's not possible to say "I depend on the email module version 2.2" unless the email project author takes care to keep the module version and module project version in sync.

Basically there seems to be no relationship between "module versioning" and "module project versioning", which can only be confusing. It's not totally clear that both concepts need to exist. Perhaps this could be rethought and simplified for Zorba 3.0.