Comment 3 for bug 1352745

On another project I used a combination of libmemcached-1.0.16 and pylibmc-1.3.0 successfuly (on CentOS 6). There's no thought put into upgrading to latest and greatest here, I just happen to know both of these work together. I have logged in to karlstaging and both libmemcached-1.0.16 and pylibmc-1.3.0 seem to build OK there. I think what I'm going to try to do is:

- Add code to osideploy which puts a version of libmemcached-1.0.16 into /srv/{whatever}/opt/libmemcached-1.0.16
   via "./configure --prefix=/srv/{whatever}/opt/libmemcached-1.0.16 --without-memcached" if it doesn't
  already exist there.

- Remove the cmmi recipe for libmemcached from the buildout.cfg generated by osideploy app server template.

- Change the recipe for the pylibmc egg in the buildout.cfg generated by osideploy app server template to use an
  -rpath of "/srv/{whatever}/opt/libmemcached-1.0.16" and update the version of pylibmc in the version pins to 1.3.0.