On Wed, Sep 9, 2009 at 2:23 AM, Stanislav Malyshev<s...@zend.com> wrote: > Hi! > >> The question is: Do you want fpm-sapi (or not)? > > If it applies cleanly to PHP and doesn't require changes in the core, then > why not? > But for that I guess there should be some build modifications that make > common build (i.e., as for other modules - one runs configure/make and gets > the binary) - is it possible? If so, then I see no problem making sapi/fpm.
Its coming with it's own ./configure. I think you can hang one configure script off from another because that's how fpm configures its libevent library. This would be much preffered way. However you'd then also have to be forwarding the fpm-specific configure flags onward from the main php configure script. Im not sure how to do that yet. But once the Makefile is created, then make-stage is like an automatic recursion thing isn't it? BTW all the debian maintainers asked for is the fpm sourcecode to be supplied in the php-src folder. (rather than created from a patch file). They said nothing about requiring to share the same build command. I mention this because it didn't represent any kind of technical issue for making a debian package. Indeed it seemed easier not to. > Not sure about bundling libevent though - does it have to be bundled? Don't know. Libevent is frozen in there and a couple of files were modified with references back into the fpm headers. The Libevent was updated recently anyway, so its a pretty recent version. dreamcat4 dreamc...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
