Andreas Jung wrote:
--On 30. Oktober 2006 00:01:33 +0100 Philipp von Weitershausen
<[EMAIL PROTECTED]> wrote:
* It is unclear to me at this point what Zope 2's egg story will be. I
*hope* that 2.11 will get the same egg story as the Zope 3.4 that ships
with it does, though noone has talked about eggifying Zope 2 yet. We
should probably do that.
What are our benefits from a Z2 Eggification. Eggification is basically
about packaging and distribution of components with little dependencies
in order to re-use them in other contexts. However most components of
Zope 2
are heavily dependent on others. Or are we talking about using Zope 3
eggs within Zope 2 as part of the Zope 2 distribution process?
I would argue a bit of both. Zope 2 can be a giant egg without much
difficultly enabling use of easy_install and dependency management in
relation to that egg(think of how products depend on a version or point
version of zope2). As an egg friendly installable, it can then be used
in egg recipes etc.
it also lets us start teasing parts of zope2 out of the monolith of
zope2 their own eggs(ZTC comes to mind) so they can evolve at a rate not
controlled by the zope2 release process.
Since it is possible to match dependencies, releases can be built from
egg recipes dynamically rather than cumbersome bundle linking. I'm
guessing this would make release management ultimately easier and more
consistent; a recipe would simply match all stable and compatible eggs
to the zope version that needed them.
-w
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
