I'm running into the problem where if I run buildout directly while doing this, it starts getting site-packages from the system wide directory which has a different version of zope and so buildout errors out. This happens even though I have virtualenv enabled.
<br>It's the same exact problem I was having with grokproject before I started using virtualenv. Now grokproject is fine and it takes site-packages from $virtual/ but buildout even when I use virtualenv is taking site-packages from /usr/lib...
<br><br>So my only solution is to use Sebastian's method and use grokproject to install the app.<br><br><div class="gmail_quote">On Jan 15, 2008 8:50 AM, Luciano Ramalho <<a href="mailto:luciano@ramalho.org">luciano@ramalho.org
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Jan 15, 2008 4:57 AM, daniel <<a href="mailto:daniel.carraher@gmail.com">
daniel.carraher@gmail.com</a>> wrote:<br>> Hey,<br>> Once I checkout PlainLoginDemo, is there an easy way to get grok to load it<br>> as an application? I can place it in Sample/src/PlainLoginDemo but it<br>> doesn't get picked up by grok which is only looking in Sample/src/sample.
<br><br></div>I've been using the standard procedure to install PlainLoginDemo and<br>LoginDemo in any machine where I need to work on it. Namely:<br><br># checkout code from svn:<br>$ svn co svn://svn.zope.org/repos/main/grokapps/PlainLoginDemo
<br>$ cd PlainLoginDemo/<br>$ python2.4 bootstrap/bootstrap.py<br>$ bin/buildout<br><br>And that's it. After lots of downloads, you can test and start the app:<br>$ bin/test<br># ... test results should be OK<br>$ bin/zopectl fg
<br><br>This is the usual way to try any grok app in our repository, and has<br>been working for me and my co-workers. We all use Ubuntu Linux 7.10<br>with Python 2.4.<br><br>Regards,<br><font color="#888888"><br>Luciano<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><br>-- Daniel