On 18.07.09 02:07, Tres Seaver wrote:
> Andreas Jung wrote:
> > On 16.07.09 15:58, martin.gfel...@comit.ch wrote:
> >> Dear all
> >> I've managed to install it, largely thanks to the hint from Andreas
> >>> I haven't got a C compiler installed - I assumed the purpose of
> the Zope Windows egg was that
> >>> I wouldn't need to compile?
> >> I found all the required packages on PyPI - but in two cases, the
> latest version didn't have a Windows egg.
> >> I changed requires.txt for the two packages to require a specific
> version, which have a Windows egg.
> >> This installed zope.security == 3.6.0 and zope.hookable == 3.4.0
> without problems.
> >> My Questions:
> >> - Will the final Zope 2.12 egg have specific versions for its
> > We should ensure that. Thanks for pointing this out.
> >> (otherwise, how do you
> >> get consistent installations)?
> > Your installation won't finish since all versions are pinned.
> >> - Is there an option in SetupTools that ignores versions of
> packages which would need to compile? This
> >> could be very useful for Windows users, who are afraid to compile.
> > We have to provide windows binaries for all related egg - our task.
> Ideally we would use some of the KGS tools + something like buildbot to
> automate the building of those Windows binaries: few of the core
> developers can build them easily by hand.
I was thinking about using the XMLRPC API of PyPI for checking new
releases of some zope.*
packages (same approach as we are using in z3c.pypimirror). However an
automated build process
must have permissions on PyPI for each individual package in order for
uploading the windows build.
org:ZOPYX Ltd. & Co. KG
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -