Well I have a Perl CMS that generates static files, which is in this instance are PHP (similar in intent to Bricolage, but on a much smaller scale). However, there is a new requirement, where some of the content needs to be dynamic, and the solution has been for the Perl backend to generate the files to disk and then use LWP to fetch the content via the webserver and then display it. This is pretty yucky and inefficient, so I figured PHP::Interpreter could be the solution.

Since Apache is already installed with various other modules, I figured that it's too late to add PHP as a static build without building all other modules and Apache from scratch too, hence attempting to build it as an Apache module. However, I now see that the alternative to PHP::Interpreter, PHP, doesn't work with PHP built as an Apache module, so I guess the same reasoning applies in this instance...