-----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   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).

We've had zpkg-related bugs after *each* Zope 2.9 release;  there are a
couple of open ones now for 2.10.  Andreas, as release manager, doesn't
like zpkg or want to continue using it.  I don't see this as a "new
feature":  in fact, it restores some "old" features (e.g., out-of-tree
builds) lost in the switch to zpkg.

I agree that "Bugs Fixed" is not appropriate.  We can reclassify it in
the changelog as "Other Changes", or soemthing.

I would argue that the patch is minimal enough to apply to 2.9.4 and
2.10 final without significant risk.


Tres.
- --
===================================================================
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEnSzU+gerLs4ltQ4RAmXIAKCzDaHnVhVjx53xvcGELLzoN5T/gQCeOXyd
Bh7NITbF1N7CyXjFCklZuXg=
=p580
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to