I've fixed the various scripts etc. in the CVS so that I can now install a ZEO client/server setup. The way it actually ended up working is:

- runzope.py and zopectl.py are moved to Zope/Startup/run.py and Zope/zdaemon/zopectl.py respectively
- bin/mkzopeinstance now takes a "-z/--zeo host:port" which sets up a custom_zodb.py in the new zope instance home
- bin/mkzeoinstance now overrides less, because...
- ZEO/mkzeoinst.py generates an additional script, runzeo, which is the "runner" for the ZEO server. Both it an the zeoctl script need to know about the ZOPE_HOME, so that's been added to the scripts (via the params)
- fixed setup.py so it installed ZEO/schema.xml

 - the scripts won't be in the user's $PATH, so override that lookup
   in from mkzeoinst.py in the mkzeoinstance script
 - the scripts won't be executable, so prepend commands with $python

when vid <> ZERO.  Also, rename a local variable.

_dotxnundo(): Fix insertion of information into the currentVersions
table.  Key should be vid and value should be revid.

_collect_objs(): It's possible the vid,revid pair has already been
deleted so catch DBNotFoundErrors.

These seem to fix the last of the BDBFull test failures.

      - Collector #683: WeDAV request without XML preamble
        were not recognized by Zope and raised an exception.

the --quiet parameter.

versions were much too verbose by default.

testrunner.py last week.

configuration file template (reflects recent addition of a "products"
key to the template).

When this is done, the makefile and all temp build files are written to
the directory from which you run configure.  This is to support
Tres' desire to be able to install Zope from read-only media.

Perform minor cleanups, extensions, and refactorings of setup.py and
configure.py along the way.

information on tests that fail, regardless of the verbosity setting.
This allows using -v0 or -v1, and still seeing useful error
information as the tests are run.  This is especially helpful for
large or long-running test suites.

from the filesystem.

implementation, to allow the PageTemplateFile class to override what
happens when the check is performed.

the Zope configuration file.  There is no magical search for
INSTANCE_HOME/Products; it is included as part of the instance skeleton,
but can be controlled simply changing the configuration.

it contains have been moved to the Packages/pcgi module in the cvs.zope.org
public CVS repository; it can be distributed as a separate package for those
who need it.

This corresponds to Zope 3 collector issue 129.
http://collector.zope.org/Zope3-dev/129

  underlying database adapter should convert a unicode to the encoding the
  database expects.

"makefile".  This is a little painful, since the names match in everything
but case.  It appears to be impossible to use a generated file with the same
name as a file previously in the repository, even with the help of .cvsignore.

of ZServer.

package.

new-install-branch.