FWIW, a patched setup.py that appears to compile all known Z2 and Z3 extensions successfully (at least it completes and Zope starts) which doesn't use any zpkg extensions is available at http://www.plope.com/static/misc/setup.py . I took this from the old "setup.py" before Phil checked in his zpkg fixes, and added an Extension directive for the i18nmessageid C extension. It also requires a change to two files in Zope 3: Index: security/_proxy.c =================================================================== --- security/_proxy.c (revision 40034) +++ security/_proxy.c (working copy) @@ -17,7 +17,7 @@ */ #include <Python.h> -#include "zope.proxy/proxy.h" +#include "zope/proxy/proxy.h" static PyObject *__class__str = 0, *__name__str = 0, *__module__str = 0; and Index: app/container/_zope_proxy_proxy.c =================================================================== --- app/container/_zope_proxy_proxy.c (revision 40034) +++ app/container/_zope_proxy_proxy.c (working copy) @@ -28,7 +28,7 @@ #include "modsupport.h" #define PROXY_MODULE -#include "zope.proxy/proxy.h" +#include "zope/proxy/proxy.h" static PyTypeObject ProxyType; - C On Sun, 2005-11-13 at 19:36 -0500, Jim Fulton wrote:
On Sun, 2005-11-13 at 19:20 -0500, Tres Seaver wrote: ...
Note that of all the recent changes, I would jettison zpkg-based builds *first* if our timebox is at risk; I certainly wouldn't agree with leaving the trunk frozen due to issues with a *very* recently-proposed change which provides no measureable benefit to the users (as opposed to maintainers).
Fair enough, but without zpkg there will be a lot more stitching work to do. Way too much of zope.app is stitched in at this point. That's not a problem if we use zpkg to make the distribution.
Jim
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )