[Zope-Coders] Heads up - setup.py

[Chris McDonough]

I dont know if this is a popular position, why not just a top-level
Makefile, and maybe even a "configure" script (not
autoconf-produced) that would make installing Zope on UNIX more like
installing other UNIX programs (as opposed to other Python
programs).  As far as I can tell from comments to the Zope Book,
most of the people coming to Zope aren't as familiar with Python
conventions as they are UNIX conventions.

The top-level Makefile could of course just turn around and call
"setup.py build" and "setup.py install".

"Shane Hathaway" <shane@zope.com> wrote in message
news:3D2C46F0.70501@zope.com...
> Matt Behrens wrote:
> > On Wed, Jul 10, 2002 at 09:43:49AM -0400, Shane Hathaway wrote:
> >
> >
> >>I think you're suggesting moving setup.py to <zope>/lib/python
then
> >>creating a small setup.py in <zope> that helps the user a
little.  That
> >>would be good IMHO.  The setup.py in <zope> might be a simple
wrapper
> >>around setup.py in <zope>/lib/python, with the exception that
when you
> >>invoke it with the single argument "install", it tells you that
an
> >>install location is required.
> >
> >
> > Why not just give the root setup.py that capability?  We're
already
> > overridden parts of distutils to support data file installs...
>
> Well, if you don't mind the extra "impurity", that's a good way to
go. :-)
>
> Shane
>
>
>
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://lists.zope.org/mailman/listinfo/zope-coders
>