Re: [Zope-dev] RFC: Eggifying Zope's extension mechanism ("Products")
Daniel Nouri-3 wrote: > > > BTW, compare the difference in size between that script[1] and > ploneout[2]. I should mention that it does less than ploneout (it > doesn't download Zope 2, but that'd be trivial to add) and it could be > argued that it's less flexible for some definition of flexible. (Sorry > for being OT here.) > > > [1] http://danielnouri.org/svn/scratch/Plone/trunk/install-plone.py > [2] http://svn.plone.org/svn/plone/ploneout/trunk/ > Well, I'd say that ploneout is only this big: http://svn.plone.org/svn/plone/ploneout/trunk/buildout.cfg There are svn:externals to the products and eggs. There are also generic recipes for installing zope 2 and setting up a zope 2 instance and downloading tarballs for products. These are basically this big: http://svn.plone.org/svn/plone/ploneout/trunk/src/z2c.recipe.zope2install/src/z2c/recipe/zope2install/__init__.py http://svn.plone.org/svn/plone/ploneout/trunk/src/z2c.recipe.zope2instance/src/z2c/recipe/zope2instance/__init__.py http://svn.plone.org/svn/plone/ploneout/trunk/src/z2c.recipe.distros/src/z2c/recipe/distros/__init__.py Still a bit longer than your script, but not quite so scary. :) The zope 2 install recipe is the only one that's not mostly trivial (if you consider shell and file operations trivial). That recipe tries to give you a lot of flexibility to control what the instance (and thus the deployed environment). That said, I quite like your script as an example of using workingenv from python to set this stuff up. Martin -- View this message in context: http://www.nabble.com/RFC%3A-Eggifying-Zope%27s-extension-mechanism-%28%22Products%22%29-tf3077929.html#a8730367 Sent from the Zope - Dev mailing list archive at Nabble.com. ___ 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] RFC: Eggifying Zope's extension mechanism ("Products")
Philipp von Weitershausen wrote: > > For their upcoming versions, Zope 2 consuming platforms such as Plone > are creating standard Zope3-style Python packages while still having > Zope 2 products around. This proposal aims at unifying the deployment > of products and Python packages into a Zope 2 instance alike by using > Python eggs and their entry point system. > > See > http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot > for the full proposal. Comments are appreciated. I plan on implementing > it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) > So, to be clear: - You would have lib/python/Products/CMFCore as an alternative to Products/CMFCore - Products in lib/python would be picked up by entry point rather than scanning Products/ - The entry points would work with non-products as well, e.g. if lib/python/plone/foobar had the entry point, it could be a project - This would supersede the five:registerProduct directive we have now If so, this sounds great, so +1 :) I do wonder what would happen if you had both lib/python/Products/CMFCore and Products/CMFCore, though. Would there be an explicit preference or would Zope fail to start up with a conflict? I think I'd prefer the latter, in fact, so that people don't end up modifying/upgrading the wrong code by accident! Martin -- View this message in context: http://www.nabble.com/RFC%3A-Eggifying-Zope%27s-extension-mechanism-%28%22Products%22%29-tf3077929.html#a8612115 Sent from the Zope - Dev mailing list archive at Nabble.com. ___ 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] RFC: Eggifying Zope's extension mechanism ("Products")
For their upcoming versions, Zope 2 consuming platforms such as Plone are creating standard Zope3-style Python packages while still having Zope 2 products around. This proposal aims at unifying the deployment of products and Python packages into a Zope 2 instance alike by using Python eggs and their entry point system. See http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot for the full proposal. Comments are appreciated. I plan on implementing it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ 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 )
