<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Am 30.07.2007 um 19:37 schrieb Philipp von Weitershausen:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">I'm not sure what "working in the zc.buildout" is supposed to mean. I don't consider zc.buildout evil. Not totally at least :).</font></p> </blockquote><br></div><div><div>I benefit from zc.buildout in two ways for my zope projects since i figured it out:</div><div><br class="webkit-block-placeholder"></div><div> - every-time-and-every-place reproducable development environments</div><div> - only install what is really necessary</div><div><br class="webkit-block-placeholder"></div><div>But sometimes:</div><div> - I am bothered by that .installed.cfg (I always stumble over it, because it's hidden).</div><div> - Someone already mentioned the .pyc-file misery.</div><div> - And it's not easy to find the right order for including the .zcml-files in larger projects. Maybe there is a recommended order somewhere which I didn't recognize until now. I thought about extracting it from the DEPENDENCIES.cfg and import-statements.</div><div><br class="webkit-block-placeholder"></div><div>Altogether it is really worth to dive into zc.buildout (but you should take a deep breath ;-)</div></div><br></body></html>