-----BEGIN PGP SIGNED MESSAGE-----
On Feb 16, 2009, at 13:50 , Charlie Clark wrote:
> Am 16.02.2009 um 13:08 schrieb Jens Vagelpohl:
>> I'm wondering, ist it necessary to declare a dependency where we know
>> that it is a required dependency for another dependency we already
>> declare? Specifically, if CMFDefault is declared as dependency, is it
>> necessary to also declare CMFCore because we know CMFDefault already
>> declares it?
> hm, do we always *know* that?
> Unless dealing with known behemoths aka Zope2, I'd go with explicit is
> better than implicit and expect declarations for any import statement.
Yes, that's a good point.
> Then again I'm still not convinced that the CMF itself isn't a mini-
> behemoth to be eaten tail, toenails and all.
It depends on how you look at the dependencies. If you mean
installation dependencies then I think there's been great progress
disentangling the different packages. If you mean "I don't need Y for
installing X, but really, X is not all that useful without Y" that's a
different issue. But that's off-topic for this thread ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests