Adam GROSZER wrote:
Though no idea how the above could be solved with FOSS tools.
You know Launchpad is being open sourced, right?
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.02.2009 20:18 Uhr, Hanno Schlichting wrote:
Lennart Regebro wrote:
So, I propose to have an Open Space session at PyCon, Chicago, March
27-29 .
Sounds good. Count me in.
Will be there as well.
Me too, and if
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code,
so we don't confuse people anymore with two locations doing the same.
Out of interest, where can I learn more about Zope 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.02.2009 9:49 Uhr, Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code,
so we don't confuse people
Summary of messages to the zope-tests list.
Period Thu Feb 12 12:00:00 2009 UTC to Fri Feb 13 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux
From: Zope Tests
Date: Thu Feb 12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code,
so we don't confuse people anymore with two locations
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area as retired after moving the code,
so we don't confuse people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hanno Schlichting wrote:
I had time to work on this on our Berlinale Sprint and this is now done!
I marked the old Zope2.buildout area
Tres Seaver wrote:
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk
...
$ cd Zope-trunk
$ /oath/to/python2.5 bootstrap.py
...
$ bin/buildout
Another question...
If I have a project that's Zope 2 based, how do I specify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
At this point, the SVN trunk *is* a buildout:
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Zope-trunk
...
$ cd Zope-trunk
$ /oath/to/python2.5 bootstrap.py
...
$ bin/buildout
Another
Tres Seaver wrote:
I guess this equates to what does a Zope 2 instance look like now that
we're buildout-based?
install_requires=['Zope2=2.12dev'],
Okay, how do I get zopectl and runzope?
Where do I put my zope.conf?
Where do I put old-school products?
What would the following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
I guess this equates to what does a Zope 2 instance look like now that
we're buildout-based?
install_requires=['Zope2=2.12dev'],
Okay, how do I get zopectl and runzope?
Where do I put my zope.conf?
For the time being Zope2 must be used as a develop egg. Like e.g. so:
http://svn.zope.org/CMF.buildout/trunk/
Stefan
On 13.02.2009, at 13:49, Chris Withers wrote:
I guess this equates to what does a Zope 2 instance look like now
that
we're buildout-based?
13 matches
Mail list logo
