[development] New functionality on project nodes installed ond.o

[Clemens Tolboom]

Can you please elaborate on this 'core version' dependency?

To define a version dependency would be nice to have but the info file
contains module dependencies and not project dependencies.

Ie 'my_project' depends on module 'cclink (>=1.3)' provided by
'workflow_ng'

The expression (>=1.3) can become quite complex. See
http://www.debian.org/doc/debian-policy/ch-relationships.html as an
appetiser :-)

Cheers
 
On Fri, 2008-03-07 at 00:10 -0500, Oleg Terenchuk wrote:
> 
> 
> On 3/6/08, Derek Wright <drupal at dwwright.net> wrote:
>         
>         On Mar 6, 2008, at 11:38 AM, Oleg Terenchuk wrote:
>         
>         > what about modules that have dependency on other modules.
>         how can
>         > we specify which parent module version my module supports?
>         
>         
>         In the body of your project node and in your release
>         notes.  Drupal
>         has no support for version-specific dependencies, so you need
>         to
>         communicate these via the text channels of communication, not
>         automagically.
>         
>         -Derek (dww)
>         
>         
> 
> 
> 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
> 
> what stops from having modules be able to specify module dependency
> version based on what dependency they specify in the .info file ? 
-- 
Clemens Tolboom
build2be
KvK NL020994130000

info at build2be.nl
http://build2be.nl
+31(0)6 10 27 96 95