Have some questions about module dependencies:

1. When module depends on one of system modules (eg Mailer, Categories) - should it be mentioned?
2. Some times module dependencies are optional; eg I'm writing newsletter module, which will allows (as an option) to use Pagesetter as tool to create newsletters. So in some cases Pagesetter can be required. How to define such dependency? As "PNMODULE_DEPENDENCY_RECOMMENDED"? In this case some comment to dependency would be suitable, but there is no possibility to add comment to module dependencies.

Thanks for any suggestions!

--
Polish Zikula Team
Bianor Works - my Zikula works on CoZi

1. I think it would be sensitive, since somebody could for example uninstall Mailer.
2. Your module still does what it should also if Pagesetter is not installed. Therefore I suggest to declare it as recommended. Adding comments to module dependencies is a nice idea, but because of the ongoing feature freeze it will not be part of .8, so you should open a feature request for this.



edited by: Guite, Aug 05, 2007 - 11:10 AM

--
Guite | ModuleStudio

Guite - thanks for reply.

But I'm wondering about first question and your answer...
Looked to system modules and I've saw that every module can be removed - even pnRender, which is required for all other modules.
So I'm wondering if system modules need to be mentioned in module dependencies - because in fact there is at least 10 required modules for module on which I'm working (eg Mailer, Categories, Profile, Users, Permissions...) and almost all of them are recommended

Perhaps we should make an assumption that all system modules are required or recommended since removing them can entirely make useless not only a single module but also an entire system?



--
Polish Zikula Team
Bianor Works - my Zikula works on CoZi