Shawn,
Please see the other thread I started about distutils vs. make. If the
resolution is to just stick with make, then there won't be any need to
do anything with setup.py.
My hope was that one could do the following (when cherrypy isn't on your
system):
hg clone ... ips
cd ips\src
python setup.py install
python setup.py test
and everything would build and the unit tests would run, including
whatever is necessary with cherrypy to make this work.
Tom
Shawn Walker wrote:
2008/5/22 Tom Mueller (pkg-discuss) <[EMAIL PROTECTED]>:
My request was for setup.py to be able to obtain the cherrypy distribution
like the Makefile (if the tar.gz file is not going to be checked into hg),
not to build an SVR4 package for cherrypy.
I misunderstood then.
So is it acceptable to have setup.py grab the CherryPy tarball if it
doesn't exist?
That still wouldn't build it and install it into the proto area.
Cheers,
begin:vcard
fn:Tom Mueller
n:Mueller;Tom
org:Sun Microsystems, Inc.;Update Center/OpenInstaller Software
adr:;;21915 Hillandale Dr;Elkhorn;NE;68022;USA
email;internet:[EMAIL PROTECTED]
title:Senior Staff Engineer
tel;work:877-250-4011
tel;fax:877-250-4011
tel;home:402-916-9943
x-mozilla-html:TRUE
version:2.1
end:vcard
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
