Conclusion

clemens — Mon, 03 Mar 2008 10:07:17 +0000

My conclusion would be to make module.inc the key module for module and project dependency management.

Changes to install.php, system.module, update.php are relative easy to do afaik.

What i haven't covered is schema update dependencies.

Steps to take:

make drush_mm more robust as a showcase
patch module.inc with lessons learned from drush_mm
provide the project provides files same like status_update
with this into place drush (D7) could have lean and mean drush_pm and drush_mm modules

module dependency management

clemens — Mon, 03 Mar 2008 08:55:21 +0000

I don't like the idea that dependencies are not handled in a unified way. By that I mean that both module.inc and update.php code is written to handle module status. There should be a central library handling their dependencies. When we handle this in a unified way installing a big project like ubercart is easy.

When installing/enabling a module it is important to know what this module is dependent of. Ie uc_cart is dependent of uc_order. See ie http://build2be.com/sites/build2be.com/files/ubercart.neato.png

build2be/com/e - module.inc

Conclusion

module dependency management