Tres Seaver wrote:
Log message for revision 68810:
Note dropping of 'zpkg'; use a current version number.
Changed:
U Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt
U Zope/branches/tseaver-retire_zpkg/setup.py
-=-
Modified: Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Tres Seaver wrote:
Log message for revision 68810:
Note dropping of 'zpkg'; use a current version number.
Changed:
U Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt
U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
I worked last night with folks from the Fedora Extras project who were
trying to package Zope 2.9.3 for FC5+. Because they were working from
the release tarball, generated by 'zpkg', much of my knowledge about how
the build
Thanks a lot for your work!
--On 24. Juni 2006 09:40:36 -0400 Tres Seaver [EMAIL PROTECTED] wrote:
Remaining TODOs:
- I would like to have a few more folks try out working with the
tarball, which I have uploaded to zope.org:
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux
zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 6317
Blamelist:
andreasjung,benji_york,ctheune,dominikhuber,hdima,jens,philikon,tseaver,yuppie
BUILD FAILED: failed test
Tres Seaver wrote:
I believe that the extra flexibility which zpkg is intended to provide
(dependency-based subset distributions, primarily) would be better
served by moving Zope to use eggs,
Where are the eggs, btw?
I will be ready shortly to merge this branch to the 2.9 branch, the 2.10
Tres Seaver wrote:
Since you're denoting this as a current version number, do I take it
that you're planning on changing the way Zope 2.9 and 2.10 releases are
created as well? I would consider egg-based deployment a feature; at
least it's a big enough change that I'd be worried for it to
Chris Withers wrote at 2006-6-23 17:12 +0100:
Get this error on startup with one project I've just moved to Zope 2.9.3:
File /usr/local/zope/2.9.3/lib/python/Zope2/Startup/datatypes.py,
line 175, in createDB
return ZODBDatabase.open(self, databases)
File
Tres Seaver wrote:
The point is that the release tarball should generate the same
environment that the developers routinely work in; otherwise, we leave
the poor suckers who install from it stuck with whatever bugs are caused
by the difference.
Ok. I'll note that Python eggs don't fulfill
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Tres Seaver wrote:
The point is that the release tarball should generate the same
environment that the developers routinely work in; otherwise, we leave
the poor suckers who install from it stuck with whatever
On Sat, Jun 24, 2006 at 04:08:23PM +0200, Andreas Jung wrote:
| - Make the corresponding changes to the Windows build machinery.
|
|
| Perhaps we should check the Windows build machinery before merging the
| branch.
| It's easy to mess up the Windows stuff but it's hard to fix it :-)
I can
Tres Seaver wrote:
That will be good. Even after eliminating the list you provided (see
below), there is still a lot of stuff in zope.app which is irrelevant to
Zope2 (I think).
Agreed. By the way, I just compated a Zope 2.9.3 install with your
tarball. The same comparison should be done
12 matches
Mail list logo
