<br><br><div><span class="gmail_quote">On 3/6/08, <b class="gmail_sendername">Derek Wright</b> <<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
<br> On Mar 6, 2008, at 11:38 AM, Oleg Terenchuk wrote:<br><br> > what about modules that have dependency on other modules. how can<br> > we specify which parent module version my module supports?<br><br><br>In the body of your project node and in your release notes. Drupal<br>
has no support for version-specific dependencies, so you need to<br> communicate these via the text channels of communication, not<br> automagically.<br><br> -Derek (dww)<br><br><br></blockquote></div><br><br>it was possible to do the same thing for drupal core support, and yet it was impleneted to be an automatic thing in the project module on d.o<br>
<br>what stops from having modules be able to specify module dependency version based on what dependency they specify in the .info file ? <br>