setup.py (was Re: [Zope-Coders] RE: [Zope-Checkins] CVS: Zope/doc - INSTALL.txt:1.32)

[Matt Behrens]

> I'm a little confused about the Makefile ideas, though.  Almost all 
> Python packages have a setup.py *instead of* a Makefile.  What does the 
> Makefile do?  And isn't that a problem for Windows installs, where there 
> is no "make" command?

In the installer branch, more is done besides just installing the Zope
packages into a software home.  There is also a control script that gets
installed and system-wide configuration files for that script.  Consider
configure and Makefile the UNIX entry point for using Zope as an
application as opposed to a set of packages.  Very little in either of
them makes sense on Windows.  They facilitate getting from 0 to Zope on
UNIX-like systems.

Yes, it's a problem for Windows, but nobody has stepped forward to do
the Windows half of my branch, and I'm not a Windows developer. :-)  So
I settled for not breaking anything that already exists, and trying to
write the control script in a way that will make it possible and
hopefully easy to implement Windows support when someone does step up.