Allow specifying module dependency version for a feature

Forgive is this is a sore topic. I searched the queue and did not find anything related to this.

I have been using features heavily lately and many times the features are large, requiring multiple modules. When I moved the features over to the demo server I ran into several issues related to modules not found within one of the dependencies. It turns out, the modules versions I used on my localhost did not match what was on the demo server. It seems that when enabling the feature via drush, drush will download the stable version of the module that is required.

For example, both uuid and references have sub modules only in specific versions of the modules... Drush downloads the stable version and uuid_path submodule is not available to enable, so features break.

Is there a way to speck out the version of the module dependency in the myfeature.info file?

Thanks!