My ZODB article says little about installation, because there's no good answer at this point, beyond installing all of Zope and adding $ZOPE/lib/python to your PYTHONPATH. Next week I'm going off to California for a few days, and will have lots of time to kill, so I'd like to package ZODB separately. Question: how does DC want to do this? If I was following my own heading, I'd use the Distutils to separately package ExtensionClass, ZODB, and anything ZODB depends on. But I'd like to make this packaging official; what would DC like to do? Another point: I understand that packagizing all of Zope is on the TODO list, but it's such a big job that it won't be done any time soon, certainly not for 2.2. ZEO isn't released yet, though, so it can be placed in its final position in an otherwise-empty package. What would that location be, and what would be the package arrangement for Zope? zope.ZEO, zope.ZODB, zope.DocumentTemplate, &c., or something else? I leave on Sunday, so this needs to get this settled before then in order for me to know what to do while away. -- A.M. Kuchling http://starship.python.net/crew/amk/ Imagine a world where nothing is stable. In the West, we have three moving elements -- Air, Fire, Water -- but at least we can depend on the fourth. -- Philip, in Peter Greenaway's _8 1/2 Women_ (1999) _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
