This work has nothing to do in erp5-component branch, and is preventing it
from being merged to erp5 banch more often.
Conflicts because of non-reverted
6d1a9805 have been resolved to that its
intent is preserved with non-cluster ERP5 SR.

This reverts commit 77976a14.
This reverts commit 7aa1d92c.
This reverts commit 80062015.
This reverts commit 36ed58f2.
This reverts commit 1fe3f466.
This reverts commit 7731726a.
This reverts commit eb2016c4.

User (with enough privileges) must be supplied, otherwise logs are never
reopened.
Also, quote socket and binary paths.

update md5sum that should be part of 80062015 (Jinja2 does not support "is not" operator).

In preparation for better ERP5 clusterisation.

This reverts commit fdb2b87b.
This breaks erp5 test runner (maybe it does not accept IPv6 in SQL
connection strings).

Also, make it optional.

Unused since egg bump from commit 80bfb5e0 .

It is not used in xwiki and lamp, does not work out of the box in erp5, and
prevents erp5 from moving further toward IPv6 support.
Do not drop its component SR and recipe just yet, as it might find some
use in the near future.

Based on work by Romain Courteaud <romain@nexedi.com>.

Mainly to get erp5.util.taskdistribution fixes.

revert 'stick to Zope 2.12.22' because now we introduced a workaround for performance decrease in Zope 2.12.23.

This reverts commit 5584482e.

stick to Zope 2.12.22 because Zope 2.12.23's ObjectManager.__getitem__ is much slower for a module having lots of sub objects (same as d69b76ed, that seems lost by a careless merge).

Kept backward compatibility about "production" software_type.