On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting hanno...@hannosch.eu wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk
tree based on externals in sync with the Zope2 buildout and its KGS
definition and it seems I failed yesterday.
I'd suggest we reorganize the Zope
Lennart Regebro wrote:
On Tue, Feb 3, 2009 at 13:56, Hanno Schlichting hanno...@hannosch.eu wrote:
It becomes somewhat hard and annoying to keep the old full Zope trunk
tree based on externals in sync with the Zope2 buildout and its KGS
definition and it seems I failed yesterday.
I'd suggest
I don't think you faired that badly. ;-)
One obvious problem is the removal of the 'defaultSkin' directive,
which is still in use by CMFDefault. The rest looks harmless.
I am not opposed to ditching the trunk, but I don't think keeping it
in sync (if only for a transition period) is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.02.2009 13:56 Uhr, Hanno Schlichting wrote:
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Mon Feb 2 12:00:00 2009 UTC to Tue Feb 3 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test
On Tue, Feb 3, 2009 at 19:44, Hanno Schlichting hanno...@hannosch.eu wrote:
It would mean buildout becomes a requirement for the development of
Zope2 itself.
Oh, +1 to that.
For the devlopment with or on top of Zope2 any system that can deal with
normal Python distributions would work. In
