Hi.
I'm reconfiguring my dev setup for the freshly merged new installer. My
zope instances refuse to load the products from the Products directory
but don't complain. Here my configured Pathes:
SOFTWARE_HOME
/home/zagy/zope/servers/Zope-HEAD/lib/python
ZOPE_HOME
I'm slowly fumbling my way through the massive changes of the latest
branch merge... am I missing where the open databases (Globals.opened)
get closed, or did that just get dropped entirely (and if so, how does
that relate to the goals of the clean shutdown work)?
Also, now that the hacked
'make install' should not create files in the source tree as long as
you've run 'make' beforehand. Which files does it create?
On Wed, 2003-03-19 at 01:04, Adrian van den Dries wrote:
Small problem.
The 'make install' step creates files in the source tree. It probably
shouldn't do this,
Fred L. Drake, Jr. wrote:
Chris Withers writes:
Will I have to change the way Zope is built and/or the etsts are run?
Yes.
If so, where could I find otu what they now need to look like?
There is a scenario for Linux in the newinstallbranch.xml in
Packages/TestScripts; I'll test it again
On Tue, 2003-03-11 at 14:41, J Cameron Cooper wrote:
Dunno, but what sort of integration are you expecting? Most things that
work in any Python app (with the proper versions) can be made to work
with Zope without too much trouble. Whether someone's made a Product
around it is a different
Dieter,
Ok.
But I was talking only about implementation of server side function and,
I think, it is possible use python specialities without desagree XMLRPC
cross language technology. In this case, only '*' arguments.
If I make a call like Foo( 1, 2 )
The server side implementation could be
On March 20, Chris McDonough wrote:
'make install' should not create files in the source tree as long as
you've run 'make' beforehand. Which files does it create?
These directories and everything below them:
./build
./lib/python/build/lib
./lib/python/build/lib.linux-i686-2.2
