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

[Matt Behrens]

> >>I like your work, but do you envision allowing people to run directly 
> >>from the source directory, as easily as they can today?
> > 
> > That's certainly a requirement in my case.

Sure.  Development of the Zope core has to happen somewhere, right?  I
do development in a CVS checkout, and I would be most miffed if I had to
install every time I made a change to try my changes out.

(Actually I'm getting really testy running the installer ten million
times over the course of writing this whole getup in the first place,
but that's neither here nor there.) :-)

However, I did not cover the actual case of making it easy to run in the
source dist, in the absence of wo_pcgi.py.  start/stop scripts as you
know them aren't created.  But see below...

> >>Since you presumably intend to get rid of wo_pcgi.py, something else
> >>needs to create a script that can start and stop Zope from the
> >>source directory.
> > 
> > Why does something have to *create* that script?  It would be much
> > better if the script was part of the CVS tree IMO.
> 
> Sometimes I overlook the obvious.  Indeed you're right. :-)

Should actually be a piece of cake.  ZopeControl (soon to be
App.ExternalControl) contains the code that starts and stops instances.
 Normally it's imported by the 'zope' master control script machinery,
but there's no reason a script couldn't exist in the source tree root to
 import App.ExternalControl on its own and call its stop, start, et al.
routines, to run within the source tree.