Hi,
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I would
like to start a discussion about the pros and cons, risks and advantages of
any eggification effort.
Chris favors a 'big' Zope egg with some
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I would
like to start a discussion about the pros and cons, risks and advantages
of any eggification effort.
Chris favors a 'big' Zope egg
Summary of messages to the zope-tests list.
Period Sun Mar 23 12:00:00 2008 UTC to Mon Mar 24 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Sun Mar 23 21:53:19 EDT 2008
URL:
On Mon, Mar 24, 2008 at 9:00 AM, Andreas Jung [EMAIL PROTECTED] wrote:
So before promoting the eggification as an ultimate goal, let's discuss
what we really need and want. A complete eggification just for the sake of
eggs is possibly not the goal :-)
The goals as I see it is probably to
Philipp von Weitershausen wrote:
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I would
like to start a discussion about the pros and cons, risks and advantages
of any eggification
Previously Martin Aspeli wrote:
I'm not sure this is all that useful. For Plone 4, we're just going to
have a number of plone.*, plone.app.* and Products.* (and a few others,
like kss.*) eggs that we can put in a KGS or version pin in a single
Plone egg.
For Plone 4 we may also collapse
Paul Carduner wrote:
Log message for revision 84912:
add ignores
Property changes on: gocept.bsquare/branches/pcardune-setup/src
___
Name: svn:ignore
+ gocept.bsquare.egg-info
I think people generally treat .egg-info
Previously Benji York wrote:
I think people generally treat .egg-info directories like .pyc files,
they add an entry to their ~/.subversion/config global-ignores (at
least I do wink).
If you have custom entry points or local plugin you need to handle
.egg-info differently.
No need to
Wichert Akkerman wrote:
Previously Benji York wrote:
I think people generally treat .egg-info directories like .pyc files,
they add an entry to their ~/.subversion/config global-ignores (at
least I do wink).
If you have custom entry points or local plugin you need to handle
.egg-info
