I sometimes use the UnifiedInstaller, and other times use the ZopeSkel approach that Martin Aspeli documented so thoroughly.
I like to install a private python in /usr/local, and try to prevent polluting its site-packages with anything but essentials like setuptools, paster, virtualenv...
Here's a succint list of commands I used to bring it up using that python:
sudo /usr/local/python/2.4.4/bin/easy_install setuptools sudo /usr/local/python/2.4.4/bin/easy_install -U ZopeSkel /usr/local/python/2.4.4/bin/paster create -t plone3_buildout me2 cd me2 /usr/local/python/2.4.4/bin/python bootstrap.py bin/buildout -Nv
This failed because it couldn't find the python imaging library:
ImportError: No module named PIL
I updated the buildout.cfg file to include:
[buildout] parts = plone zope2 productdistros instance zopepy PIL eggs = elementtree PIL [PIL] # Build egg with Chris McDonough's custom packaging of setuptools-compatibile PIL # http://article.gmane.org/gmane.comp.web.zope.devel/13999 recipe = zc.recipe.egg egg = PIL==1.1.6 find-links = http://dist.repoze.org/PIL-1.1.6.tar.gz
When I ran buildout again, it build PIL against the system libraries on my OS X box.
I was then able to start up the instance and go to the ZMI and add a Plone Site.
bin/buildout -Nv bin/instance fg