If you've got the environment to build binaries, just use the Unified Installer. You can even use the "--with-python=..." if you'd prefer your system's Python.
On Fri, Jan 21, 2011 at 8:35 PM, rbrewer <[email protected]> wrote: > --On January 12, 2011 2:57:56 AM -0800 "Stefan Lange [via Plone]" > <[hidden email] <http://user/SendEmail.jtp?type=node&node=5950160&i=0>> > wrote: > > > Hi, > > > > I've found a solution to this issue: you have to install a newer PIL > > version. > > > > Grab it from here: > > http://effbot.org/downloads/Imaging-1.1.7.tar.gz > > > > Then install it so that your instance can use it. > > Now you have to take care that the PIL egg (that came with the Plone > > Installer) will no longer be used. Just remove (or comment) the > > corresponding entry in the zinstance/bin/instance file. > > I'd rather install any new PIL version inside the Python instance provided > by Plone, rather than use the system python. Are there any step-by-step > instructions on how to make buildout download & use a newer version of a > package? My exploratory attempts to modify the buildout.cfg file did not > succeed. > > While I would like to resolve this problem swiftly, I also want to leave > things in a maintainable state, so when I upgrade to the next Plone > version, things don't break again. > > -- > Robert Brewer > http://excitedcuriosity.wordpress.com/ > > ------------------------------ > View this message in context: Re: _imaging.so not > found<http://plone.293351.n2.nabble.com/imaging-so-not-found-tp5887646p5950160.html> > > Sent from the Installation, Setup, Upgrades mailing list > archive<http://plone.293351.n2.nabble.com/Installation-Setup-Upgrades-f293353.html>at > Nabble.com. > > _______________________________________________ > Setup mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/setup > >
_______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/setup
