Re: [Zope-dev] [Zope 2.12] Eggification of Zope 2 - pros and cons?
Andreas Jung wrote at 2008-3-24 09:00 +0100: > ... >Chris favors a 'big' Zope egg with some dependencies (like ZODB) stripped >out. I would prefer a more broader approach. One of the reasons are >company-internals modifications to the Zope core. Right now we maintain a >more or less heavy modified version of Zope 2.8 in our repos (making Zope >upgrades >pretty hard). A better modularization would help us here. I object that upgrades are "pretty hard" and I doubt that modularization would help in any way: Upgrades are hard only when local modifications and global ones interfere. This does not happen too often and how often it happens is independent from the modularization. -- Dieter ___ 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 )
Re: [Zope-dev] [Zope 2.12] Eggification of Zope 2 - pros and cons?
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 simplify the buildouts, with less "parts" directories, and get everything in a consistent way, i.e. eggs. Also the eggification should simplify for repoze-style things, and as mentioned to replace some modules more easily. I think at least that as a start ZServer and ZPublisher should be separate eggs (if eggs at all, in fact) and all the Products.* stuff should probably be separate eggs as well. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ 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 )
[Zope-dev] [Zope 2.12] Eggification of Zope 2 - pros and cons?
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 dependencies (like ZODB) stripped out. I would prefer a more broader approach. One of the reasons are company-internals modifications to the Zope core. Right now we maintain a more or less heavy modified version of Zope 2.8 in our repos (making Zope upgrades pretty hard). A better modularization would help us here. Another example: the Plone people maintained a Zope 2.10 branch with experimental ZODB blob support. With an eggified version of ZODB you could easily switch the eggs (easily spoken). 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 :-) Andreas pgppXfc9cvnRV.pgp Description: PGP signature ___ 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 )