[From nobody Tue Oct 18 22:56:48 2005
Return-Path: <tim.peters@gmail.com>
Received: from ns2.zope.com ([63.240.213.250] verified)
	by digicool.com (CommuniGate Pro SMTP 4.2)
	with ESMTP-TLS id 8185383 for jim@zope.com;
	Tue, 18 Oct 2005 16:27:55 -0400
Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.206])
	by ns2.zope.com (Postfix) with ESMTP id 4049116822C
	for <jim@zope.com>; Tue, 18 Oct 2005 16:21:31 -0400 (EDT)
Received: by xproxy.gmail.com with SMTP id s14so1022728wxc
	for <jim@zope.com>; Tue, 18 Oct 2005 13:21:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=tJFwR2PWuxxLjKEjiZ+o2lyzLVrYBtNor3tPGMPryRaEq+wA+dKD7Tc5MwmNLaWZ3oO4U0B7RsI/E/YZAATH+Vrvdd5I26LHuNVUHmW2x1FTemUTDgunnbpBITGyubKeH7iXqJgSKQljE9DyM7WBNukbRtFGQpc0vyc9WJdzG0w=
Received: by 10.70.26.17 with SMTP id 17mr2987832wxz;
	Tue, 18 Oct 2005 13:21:30 -0700 (PDT)
Received: by 10.70.132.16 with HTTP; Tue, 18 Oct 2005 13:21:30 -0700 (PDT)
Message-ID: <1f7befae0510181321u39db926pa301f3e5a0695f09@mail.gmail.com>
Date: Tue, 18 Oct 2005 16:21:30 -0400
From: Tim Peters <tim.peters@gmail.com>
To: Fred Drake <fred@zope.com>
Subject: Five status on Zope trunk (was Re: [Zope-dev] Mountpoints)
Cc: jim@zope.com, Chris McDonough <chrism@plope.com>,
	zope-dev@zope.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

[Tim]
>> I'm copying Fred because he may remember more about this than I do.
>> Fred, do you know of a reason why I can't stitch a newer ZODB into
>> Zope(2) trunk?  I have a dim, fading memory of the last attempt
>> failing, and of agreeing in email to wait for the "5 guys" to "do
>> something" before trying again.  Sorry for not being more specific ...

[Fred]
> We need to do the zpkg/ZODB switch all at once because it affects how
> extensions get their include files.

Aha!  That vaguely rings another vague bell ;-)  The ZODB 3.5+ source
code spells "#include" in its C files in a different way, and that
can't work with the way Zope trunk is currently built.

> When I tried switching the Zope 2 trunk before, there was a problem due
> to Five tests failing.  I don't remember the details, but the Five-folks
> seemed to think things would be better with newer versions of Five.
>
> Since Five development is done elsewhere, though, it's hard to tell what =
the
> deal is with that.

Can anyone working on Five comment here, please?  I gather that the
first 2.9 beta release occurs in 2 weeks, and if Fred can't do his
zpkgtools work, I can't update the trunk to a newer ZODB, and then
Chris McDonough can't do his rework of mount points (the original
topic of this thread), and then (best case) the world economy
collapses.

> I snapshotted what I did get done as the zpkg-build-branch, so we can get
> back to it without duplicating work.

So there's no reason yet to be depressed ;-)
]