On Thu, Dec 24, 2009 at 9:28 AM, Michael Shadle <mike...@gmail.com> wrote: > On Wed, Dec 23, 2009 at 5:12 PM, Mikko Koppanen <mkoppa...@php.net> wrote: >> Hi, >> >> I think this is the feature (in trunk currently): >> >> http://svn.php.net/viewvc?view=revision&revision=28287 > > This is not the same, this is just an additional way to still have > static dirs defined only at compile time, or maybe environment > variable. > > Am I not explaining this properly enough? It should be supported from > the configuration file itself. This feature in trunk doesn't add > anything new for me. >
Sorry for reposting this; my last reply didn't make it onto the list due to my lovely iPod =X The most tempting reason for me to support include support (or better yet, include glob support) would be to have better control of what gets loaded for each SAPI; for instance, load module A for CLI, load module A+B for CGI, but only only module B for fpm, etc. This would otherwise only be possible by compiling each binary separately and running ./configure && make && make install for each. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
