-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> Tres Seaver wrote:
>> Vincent Fretin wrote:
>>> If I followed the commits correctly, the mkzeoinst was extracted from
>>> ZODB3 package and is now in the zope.mkzeoinstance, right?
>> Yes. I was questioning why a ZTK user, rather than somebody using an
>> appserver like Zope2, etc., would need a bin/mkzeoinst script (the only
>> thing provided by the egg, which I extracted from ZODB at Jim's request).
>> ZODB is only included in the ZTK as a dependency, because some packages
>> import it: nothing else in the ZTK configures server instances.
> Nothing in zopeapp uses it either?
Nothing in zopeapp sets up server instances, AFAIK. Lots of code in
zopeapp imports ZODB, but nobody depends on being able to set up a ZEO
> If nothing depends on it, it's less important to track it carefully. Of
> course if app servers start using it they should be tracking it, and if
> common infrastructure emerges that builds on it, it might make sense to
> push it into something more common.
BlueBream or grokproject, which generate code to set up applications,
might want to pull it in (or emit the depenency into the generated
code). Zope2 definitely needs it.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -