Hi
> what 2 or three tiers are you talking about?
The way I read:
> > 1. Utils that are used by mmbase-core classes [..]
> > 2. Utils that use mmbase-core, but core does not depend on it.
> > 3. Utils that don't use mmbase-core, and are not directly
I thought there was a hierarchy between those (3tier); the core, optional "modules"
around the core, and optional modules (around the modules around the core?).
>From my point of view that inst a Smart Thing to do, see also the discusion regarding
>imagemagick.
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.
In case a module gets "standard" and more and more modules are depending on it, the
module becomes a candidate to get into the core.
But as said, I am just a newbee regarding mmbase.
--
groets,
bert boerland
--- pinkroccade infrastructure services ---
Unless your universe is very different from mine,
you can't save time.
voice://020-5704939/ http://www.pinkroccade.nl/
