> I'm obviously for ploneenv/workingenv.
I'm obviously a bit biased towards the buildout based approach since I
worked on it, but I worked on it because I was never very happy with the
way workingenv-in-instances worked. ploneenv makes that better and
slicker, actually, and I quite like it. I'
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,
> a
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 the actual software should become eggs that we can share.
However, I'd like to try and clarify what I see as some of the
philosophical difference
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 hav
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 \
--
Daniel Nouri wrote:
> Martin Aspeli wrote:
>> It is very interesting. What worries me a bit is how we eggify the
>> existing products. Perhaps we need a script to do that. It would almost
>> certainly introduce breakage of a lot of svn:externals, since the svn
>> layout is different. We'd also depe
On 3 Feb 2007, at 20:17 , Martin Aspeli wrote:
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 w
Martin Aspeli wrote:
> It is very interesting. What worries me a bit is how we eggify the
> existing products. Perhaps we need a script to do that. It would almost
> certainly introduce breakage of a lot of svn:externals, since the svn
> layout is different. We'd also depend on Zope (e.g. PAS) and
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 Dani
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 Daniel Nouri made me aware that you ca
10 matches
Mail list logo
