Hi Marco,
I think one of the reasons hosts don't like / use PECL is trust, they
trust
what comes with the PHP core packages and consider anything else a
security
risk. Maybe a combination of better distribution, package details,
stability
(beta / alpha) etc and maybe something that deals with compatibility. IE,
compatible with PHP 5.2.1 - 5.3.0 for example.
This is precisely what I'm suggesting. Groups of extensions, classified in
terms of general usefulness + stability, released alongside PHP releases (no
question about compatibility that way.) In doze terms that would translate
to a smaller bundle of .dlls (as opposed to the 100-ish we currently get if
we download the PECL bundle), in *nix terms it would probably equate to
either a group 'pecl install' command or a bundle of rpms (or both).
Everyone can still use the routes they already use to get hold of the more
esoteric bits and pieces, but there'd be a group of recommended extensions
handy that hosts at least shouldn't be afraid to install. That in turn
should make it easier for users to get those extensions enabled.
Not sure how many of the
larger bulk hosting companies monitor these lists but maybe trying to
foster
more enagement from the bulk hosters in their concerns etc could be
useful?
Just check the list archives. Tho' I agree it would be helpful if those same
people would butt in at this point.
Again these are just the experiences I have with the hosts i've had to
deal
with whilst trying to develop an app that will run anywhere (not an easy
task I can tell you!).
Not an easy task, and made harder by the fact that stuff moves in and out of
core from/to a place hosts don't generally go.
- Steph
Regards
Marco
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
