Comment 6 for bug 397721

Stas i ran a test yesterday and found that fpm patches cleanly ontop
all the other patches on the 5.2.6 sources (u9.04).

So i've been going a different way to both of you. It's all in a blog
post http://dreamcat4.jottit.com/

Many of the compile flags for apache are worth including. I have been
planning to re-group the compile flags into $common_config,
$web_config, and then the existing apache2-build target will also have
less flags. A new fpm-build target share the $common_config and
$web_config, and just append the the '--fpm' switch to ./configure.

The new variable '$web_config' will be the flags taken out from the
apache2-build target which aren't apache-specific (libjpeg, mysql,
sqlite, etc). These flags include important functionality for a php
distribution so i think we probably need them.

I believe the path of least resistance is to add a new 'fpm-build'
target to the existing php5 source package because it's already got
all these external dependencies set up. ( libjpeg.so, libgd.so, ....
)

To have a completely separate 'php5-fpm' source package, mshadle, it
sounds like a good idea but there's some very popular php stuff (eg
wordpress, lightbox) that needs these image libraries. You'll also
need to support 3 or 4 of the most popular databases. Performance with
these things included should be fine. However make sure to specify the
"--without-mm" flag.