-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 ;-) jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmZYjAACgkQRAx5nvEhZLIEmACeNPlN1ngSkfzSzyhu3Lr3WJ70 eRAAoIzMXWda+p7qTvzPPdBwreubx+3B =ZH9k -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests