Some modules are dependent on other modules. Also, some modules are dependent on particular versions of other modules.

For example, right now CCK 1.4 works with Views 1.5. CCK 1.5, which is released, requires Views 1.6, which is in beta.

I would like to use only stable, not beta modules, but CCK is flagged as being outdated when it's dependency 1.6 is not even out yet.

Another example. I use the views_alpha_pager module. The latest release is also dependent on views 1.6, which is not released yet.

Would it be possible- and maybe it isn't, but I'm asking anyway-- would it be possible to indicate any module dependencies and perhaps set Update status to hold off on reporting an update is available until its dependencies are also available ?

Thanks,

W

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (won't fix)

version-specific module dependencies have been discussed for a long time, but the Party Line is that it's too much overhead for not a big enough problem. i agree it'd be nice, but it'll add a lot of complexity, and in a lot of cases, will cause a lot more grief and trouble than it aims to solve. so long as core itself doesn't have a notion of version-specific dependencies, update_status.module certainly won't, either.

sorry,
-derek