Code review comment for lp:~michihenning/unity-scopes-api/single-tree

Great stuff, thanks a million for that!!! One question though: how do we handle differences in version numbers of our dependencies? In theory we should depend on same APIs for both vivid and wily, but I imagine we may run into situations where we need a fine-grained control over what version we want to have in debian/control, e.g. when a package we depend on has a different name in vivid and wily.

We branched off in other projects (namely: unity-api) and we will have to be very carfeul to land same stuff and versions in both distros, so that our dependencies in debian/control make sense in both versions.