Not rare situation when you install module A which requires module B for correct functionality. But not any obstacles to deinstall module B (you may forgot about its relation to A) and module A then cease to work... May be time comes regularize this conditions? For example, we may get on board practice similar to dependencies in Linux DEB (also RPM and other) packages. In our case it looks more simple. Module may DEPENDS from some modules, if it can't work whithout them. Module may SUGGESTS to install some modules, if with them it get more functionality.
For example A DEPENDS from B and C modules:
* if you try to switch on A in admin/system/modules then appear error with message "A depends from B and C, install them first"
* you install B and C, switch on them, then switch on A may be possible
* you try to switch of B, from which depends functionality of A and D - you get error "A and C work depends of B"
With SUGGESTS we may provide more "soft" dependencies - module A still possible switch on if in it SUGGESTS present module D, but you get warning about some functionality loss.
I think this scheme may be realized in module_help() function:
function module_help($section) {
switch ($section) {
case "admin/system/modules#description":
$output = t("Description of module");
break;
case "depends":
$output = array("module1", "module2");
break;
case "suggests":
$output = array("module3");
....
}
return $output;
}
With dependencies we decrease a lot of errors with modules (de)installation process.
Comments
Comment #1
axel commentedSorry, i'm point this issue to version 4.4 firstly, but this request for CVS or future versions of course.
Comment #2
jonbob commentedComment #3
Crell commentedTook a while, but this was finally completed. :-)
Comment #4
(not verified) commented