hey, On 20/09/2009 Matthias Klose wrote: > The zope2.12 release candidate was released last week. I updated the > packaging in the zope team repository. An upload still requires some > work, because some modules still need to be packaged. These are: > > Acquisition DateTime ExtensionClass > Persistence RestrictedPython tempstorage zLOG zope.container > zope.contentprovider zope.contenttype zope.deferredimport zope.formlib > zope.lifecycleevent zope.pagetemplate zope.processlifetime zope.sendmail > zope.sequencesort zope.site zope.size zope.structuredtext zope.tal > zope.tales zope.testbrowser [zope-functional-testing] (UNRELEASED?) > zope.viewlet zope.app.form zope.app.publication zope.app.publisher > zope.app.schema > > All other zope dependencies are available as modular zope packages > in unstable. Please have a look how these are packaged, and start > packaging. As an interim solution it could be useful to include the > still missing modules in the zope2.12 package until all these are > packaged.
if i got it right then packaging the dependencies as seperate packages isn't an option for zope2.12, we'll have to include them within the zope2.10 source tarball. the reason for that is, that zope2.12 requires particular versions of the dependencies, and doesn't build even if minor versions aren't correct. the reason why i didn't finish packaging zope2.12 is the new build system. starting with zope2.12, upstream stops support for makefiles and tradiditional build system, and requires to use buildout for building instead. i didn't have time to dig into buildout yet. but as far as i know we'll have to use something like zc.sourcerelease and a custom buildout.cfg in order to build zope2.12 with local copies of the depencency zope/python libraries/modules. > I know that not the whole zope team is interested in these > additional modules, so I'm CCing the zope2.x uploaders directly to > get involved with the packaging. i removed Cc to private adresses as i guess that anybody interested is subscribed to one of the lists. > I do not want to wait with the removal of python2.4 from unstable > for too long, I think a short time without zope2.x in unstable is > ok, while having three python2.x versions is too much. But it looks > like zope2.12 based on python2.5 or python2.6 is doable for squeeze. i didn't know that packaging zope2.12 is that timeconsuming at the time that i proposed to wait with removing python2.4 from unstable. so no objections against removal of pyhton2.4/zope2.10/zope2.11 from my side any longer. greetings, jonas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
