[Framework-Team] Re: Plone 3.0 product deployment

Philipp von Weitershausen wrote: I realize Plone 3.0 will ship with both packages and old-style products. Recently I wrote a proposal that should alleviate this problem by making it possible to deploy products as eggs [1]. I thought that this would become relevant only for Plone 3.5. Now

[Framework-Team] ploneenv - Or how using workingenv for a common Zope2 project might look like ;-)

ploneenv is a one module Python script that builds heavily on workingenv and setuptools. What it does: - It creates a Zope instance for you. You always provide the ``mkzopeinstance.py`` script that you want to use as an argument. E.g.:: ploneenv ~/myzopeinstance \

[Framework-Team] Re: Plone 3.0 product deployment

Philipp von Weitershausen wrote: On 3 Feb 2007, at 22:13 , Martin Aspeli wrote: Philipp von Weitershausen wrote: You don't have to. You can still ship Plone 3.0 as a traditional tarball for now, though not one for INSTANCE/Products but one for INSTANCE/lib/python. In that tarball, you

[Framework-Team] Re: ploneenv - Or how using workingenv for a common Zope2 project might look like ;-)

I'm obviously for ploneenv/workingenv. I wouldn't have developed ploneenv otherwise. So here is my pro-ploneenv reactions. Martin Aspeli wrote: First of all, I think this is great. :) The important thing here is that people can use what they feel comfortable with - at the end of the day, all