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
> branch, and the Zope2 trunk. Here is how I have tested it so far:
> - All unit tests pass, with the same count (and deprecation warnings!)
> in my sandbox for this change as for the 2.9 head.
This doesn't surprise me. After all, you just tarred up the SVN export.
zpkg actually only tars up what is explicitly selected to be released.
Your tarball contains a few things that haven't been in Zope 2.9.x
releases before, e.g.:
Most of these
a) have either never released even in Zope 3 (this is the majority),
b) are sample things (like css, styleguide, demo, etc.) that are (for
the most part) bitrotting in zope.app
c) are so much core to Zope 3 that they don't make sense in Zope 2 (such
as twisted, securitypolicy)
While b) and c) might not do much harm, the fact that things in a) *are*
released now *does* make a new feature. Even worse, most of the things
in category a) *should not* be release because they're considered broken
or unstable. I agree that zope.app is horribly trashed with junk that
doesn't belong in there (probably doesn't even belong inside the Zope 3
tree), but that's how it is right now. Just dumping it in a tarball
isn't the way to go...
If it had been that trivial to NOT use zpkg back then, I certainly
wouldn't have considered it at all...
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -