My recommendations would be:
for (1): Let the build system spit out packages for the most well known
distributions which are similar to the windows ones, e.g. one small php
binary, many *.so in the "standard" package and a pecl *.so package.
Dedicated server owners or small web hosts usually rely on those
packages. And if they're official php.net packages they will favor them
over custom ones (see debian stable for example which is always outdated
and people have to rely e.g. on dotdeb packages).
for (2): Don't just make recommendations to webhosts, primarily make
recommendations to distributions, maybe convince them to use the above
explained packages.
Generally:
it would help to consolidate the function set of php. The more options
there are (let it be configure or php.ini options) the less portable is
php code.
Steph Fox wrote:
(1) The problem of web hosting remains, and isn't easily resolved. We
already saw what the situation is when it comes to web hosts and the
distributed .ini files; it's much the same when it comes to extensions.
The better hosts may well enable further extensions on request, but many
won't - possibly because they don't know how, or because they're in turn
relying on a distro that doesn't offer a wide range from PECL.
(2) IMHO there needs to be some way to make recommendations to web hosts...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
