> I thought it would be more wise to have something like: > 0 needed stuff (apache, IIS, Tomcat, MySQL, Sequal, imagemagick etc that is not part > of the distribution) > 1 A slim core > 2 Optional modules.
We have what I call a yoyo effect. -before the relase of mmbase to the public mmbase itstelve was a module inside a system (james?) -mmbase was relased as one module (containing everyting from config to imagemagic classes) As more developers joined and more choices can be made it's not possible / good to have everyting in one system we don't want everybody to install imagemagick or download the informix jdbc drivers to compile mmbase Anyway in cvs we started making more modules (community/ scan/ editwizards/taglib etc) What you are reffering to is how we "present" the modules in the mmbase distro (also in that we do some yoyo by adding and removing modules every distro) And what we are taking about is how to solve the depenency problem keesj -- "real developers don't want to know what's in the core"
