Thanks for your replies Philipp and Brandon,<div>Things are more clearly now :) So zopeproject _only_ deals with setting up the environment for you, when you run buildout eggs actually get installed. And, I don't need zopeproject on my hosting machine at all, I just test and develop on my personal machine and when ready, I install it as an egg on the host and run it.
</div><div><br> </div><div>Now I have the boring task of converting my old webapp done in 3.3.1 to an egg with all</div><div>dependencies. Is there a way that can aid me in adding dependencies?</div><div>As it is now I see this in front of me..
</div><div><br class="webkit-block-placeholder"></div><div>1. Look at all imports to see what I need</div><div>2. Add them in configure.zcml with <include></div><div>3. Add them in setup.py</div><div><br class="webkit-block-placeholder">
</div><div>I can also see 'file="meta.zcml"' in some includes, how would I know when to specifically include a file or not? Having to look at the zope tree for files seems kind of awkward.</div><div>Also, say that I use
zope.foo.bar, how would I know wether to include zope.foo or zope.foo.bar as a dependency? I could do a simple search on pypi for this but it seems kind of time consuming.</div><div><br class="webkit-block-placeholder"></div>
<div>Lots of questions :)</div><div>Thanks for your time </div><div>Jesper</div><div><br> </div><div><br class="webkit-block-placeholder"></div><div><br><div><span class="gmail_quote">On 11/5/07, <b class="gmail_sendername">
Brandon Craig Rhodes</b> <<a href="mailto:brandon@rhodesmill.org">brandon@rhodesmill.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
"Jesper Petersen" <<a href="mailto:instantfoo@gmail.com">instantfoo@gmail.com</a>> writes:<br><br>> I've looked a bit at zopeproject, but I'm still wondering if it's<br>> possible to still install zope as eggs without zopeproject (if that
<br>> even makes sense).<br><br>If I understand both "zopeproject" and your question (and I'm less<br>confident about whether I understand your question), then this might<br>be the answer you need: The "zopeproject" script is *not* designed to
<br>install Zope. That is, it's not, once you've developed your Zope<br>project in one place, the way you "make Zope appear" on the actual<br>hosting server so that your application can run.<br><br>Instead, "buildout" is how you get Zope installed most of the time.
<br>Your "setup.py" for your application is what will list Zope as a<br>dependency, and will result in its being fetched and installed before<br>you run your application.<br><br>So what's the point of "zopeproject"? It's just there to write your
<br>first "setup.py" and "buildout.py", to create your "src/" directory<br>for you, and get things set up for development. But once you've<br>started your project, you'll never need "zopeproject" again; you can
<br>immediately uninstall it if you want! :-) So you'll never need it<br>installed on a "production box", only on development boxes where you<br>first create projects out of nothing.<br><br>Let me know whether this answer was helpful, or a statement of the
<br>obvious that is beside the actual point of your question. :-)<br><br>--<br>Brandon Craig Rhodes <a href="mailto:brandon@rhodesmill.org">brandon@rhodesmill.org</a> <a href="http://rhodesmill.org/brandon">http://rhodesmill.org/brandon
</a><br></blockquote></div><br> </div>