Jens Vagelpohl wrote:
Let's get this discussion back from generic pie-in-the-sky to the
simple situation where we just need this one package integrated into
CMF 2.1, and quickly.
Wichert wants a Plone 3 beta very very soon, there is no time to
switch the CMF to any other packaging/buildout mechanism before that.
What happens on the trunk after the 2.1 branch is cut, I don't care.
I do care about getting the 2.1 beta out quickly. All that's missing
is merging the tool/utility stuff, which depends on having this new
Taking this into account, how should the five.localsitemanager thing
My preference would be to ship CMF 2.1 as two tarballs - one for
lib/python and one for Products, or one tarball containing Products/*
and lib/python/* (i.e. to be extracted into the Zope instance root).
If that's unacceptable, Rocky can make localsitemanager use only
relative imports and thus function as both a product and a package,
though I don't know if anything needs to refer to
Products.localsitemanager, which in turn makes it painful to use it as a
regular python package.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests