The 4.7 install system does not contain this. I'll have to check CVS. Even then, I still think this would make more sense as a module hook. It would be nice to at least see module versions on the admin/modules page. Such a system could also allow for a new module to notify admins of module updates ;) Versioning will really be important for the API modules that don't have their own interface. It would be nice to be able to release a new API under the same module name. ~Rob Khalid B wrote:
I think the install system that is under development does have dependancy checking as part of it.
On 5/27/06, Robert Wohleb <rob@techsanctuary.com> wrote:
If this was to be implemented, it should be taken further to include versioning. As more modules are interconnected, this will become more of an issue.
~Rob
Doq Doques wrote:
Hi. What about implementing hook_depend(). I mean module that depends on some module (e.g. taxonomy) must define
function modulename_depend() { return array('taxonomy'); }
Then if user has no taxonomy module turned on - he/she will be asked to do so or not. If not - he/she will be told that modulename can't be installed.
Also when user disables taxonomy module then he/she will be told that modulename depends on taxonomy module and so modulename will be also turned off.
-- ---------------------------------------------------------- It is by Caffeine alone that I set my mind in motion It is by the beans of Java, that my thoughts acquire speed The hands acquire shakes; the shakes become a warning It is by Caffeine alone that I set my mind in motion
-- ---------------------------------------------------------- It is by Caffeine alone that I set my mind in motion It is by the beans of Java, that my thoughts acquire speed The hands acquire shakes; the shakes become a warning It is by Caffeine alone that I set my mind in motion