Hello,
On Fri, Feb 13, 2009 at 20:13, Stefan H. Holek <ste...@epy.co.at> wrote: > For the time being Zope2 must be used as a develop egg. Like e.g. so: > http://svn.zope.org/CMF.buildout/trunk/ > I got it working without development egg: [buildout] parts = instance eggs = some_project zope2 # Reference any eggs you are developing here, one per line # e.g.: develop = src/my.package develop = src/some_project [productdistros] recipe = plone.recipe.distros urls = http://hathawaymix.org/Software/CookieCrumbler/CookieCrumbler-1.2.tar.gz http://www.dieter.handshake.de/pyprojects/zope/ZopeProfiler.tgz nested-packages = version-suffix-packages = [instance] recipe = plone.recipe.zope2instance # That way it looks for mkzopeinstance in the bin directory # That there should be a mkzopeinstance.py is defined in zopepy zope2-location = . zope2-egg = True user = admin:pass http-address = 8080 debug-mode = on verbose-security = on eggs = ${zopepy:eggs} zcml = some_project some_project-overrides products = ${productdistros:location} [zopepy] recipe = zc.recipe.egg eggs = ${buildout:eggs} interpreter = zopepy # This mkzopeinstance=mkzopeinstance.py is a hack. Better would be a patch for zope2instance scripts = zopepy mkzopeinstance=mkzopeinstance.py Best regards, Patrick
_______________________________________________ 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 )