Sean Coates wrote:
From my experiences the problem with this is many shared hosts wont install
non core modules, so the more modules moved from core to pecl the less
flexible php will be and the less use it will be.
I understand the need to keep the core code maintained and as clean and
lean
as possible, but we also need to look at what developers need to create
applications that can be used with mass virtual hosting.
This is a valid point, but it represents a chicken-and-egg problem.
Shared hosts are used to deploying PHP Proper and ignoring PECL, because
in the past, core was the only repository for everything.
As PECL grows in popularity (and as users demand more PECL
installations), we can hope this these hosts become more flexible.
At least that's what _I_ think.
I think we should make this a PHP6 todo item. A new major version is a
better opportunity to get a change of minds, than a creeping slow
change, which is about creating sufficient pain in our users so that
shared hosters finally get the clue.
Until then we should add extensions that we think are reasonably
frequently required and move out the ones that we deem obscure. I think
zip is quite reasonable to get added.
As for the coordination of PECL packages that are symlinked to
internals, it sounds like this really needs some thinking before PHP6,
because there are already a number of extensions affected and it does
sound like its a little bumpy.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
