for the records: http://plone.org/products/kupu says, 1.4.13 is the last version compatible with plone 2.5. but for this to work you have to do the following:
* install it as a Zope Product, not as an egg. * if you install it as an egg, pin all dependencies from setup.py and dependend products to what plone2.5 likes. * or delete install_requires dependencies from setup.py this should also work with kupu 1.4.17. best way is probably to use kupu as a Product. (for buildout based environments probably via infrare.subversion to put it somewhere and reference it in instance:products section.) note, i'll delete my https://github.com/thet/Products.kupu-plone25 repository sometime soon. best, johannes raggam i'll create a On Fri, 2011-03-11 at 17:06 +0100, Johannes Raggam wrote: > dear list, > > recently i upgraded the kupu instances of my still running plone 2.5 > installations. but at some point the kupu's of the 1.4 branch have a lot > of dependencies defined in setup.py. normally thats desireable, but a > installation for plone 2.5 will break because setuptools tries to grab a > lot of too new eggs and setup depends on plone as egg itself. but > plone2.5 is not eggified. > > i created a branch https://github.com/thet/Products.kupu-plone25 which > is plone2.5 compatible. the only change is that i removed all > dependencies and test dependencies in setup.py. what do you think of > merging it back into the 1.4 branch, so kupu 1.4 will officially support > plone2.5 - as mentioned somewhere in the docs... > > best,,,hannes > > -- johannes raggam / thet python plone zope development http://johannes.raggam.co.at/ mailto:johan...@raggam.co.at http://bluedynamics.com/ _______________________________________________ Product-Developers mailing list Product-Developers@lists.plone.org https://lists.plone.org/mailman/listinfo/product-developers
