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 =================================================================== --- Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt 2006-06-23 23:30:41 UTC (rev 68809) +++ Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt 2006-06-24 03:03:22 UTC (rev 68810) @@ -18,6 +18,9 @@
Bugs fixed
+ - Returned to the "classic" './configure && make && make install' + recipe, dropping the use of 'zpkg' for building Zope2 releases.
I don't think this is a bugfix :)
+ - OFS Application: Updated deprecation warnings. Support for '__ac_permissions__' and 'meta_types' will be removed in Zope 2.11, 'methods' support might remain longer.
Modified: Zope/branches/tseaver-retire_zpkg/setup.py =================================================================== --- Zope/branches/tseaver-retire_zpkg/setup.py 2006-06-23 23:30:41 UTC (rev 68809) +++ Zope/branches/tseaver-retire_zpkg/setup.py 2006-06-24 03:03:22 UTC (rev 68810) @@ -34,6 +34,7 @@ --install-platlib=/usr/local/lib/zope \ --install-purelib=/usr/local/lib/zope """ +ZOPE_VERSION = '2.9.4-alpha'
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 occur in a maintenance release. After all, zpkg *does* work and the way zpkg-based releases are installed *is* documented (hence protest against this being a bugfix). It just gives some people headaches (which is why I'm +1 to the overall idea). Philipp