From: Stig S. Bakken [mailto:[EMAIL PROTECTED]] > I would like to point out that moving to PECL ("pickling") is not the > same as not having stuff bundled with PHP anymore. The main point is to > separate CVS areas, so the main PHP distribution has more control on > what versions of different extensions it bundles. As good as every > extension (except ext/standard) could move to PECL, where they can live > happily with their own release cycles, and PHP be released with the > latest stable version of each it wants to bundle. > > In addition, since each PECL extension is also a PEAR package, > extensions may be upgraded individually if the extension was build as a > shared lib. > > How far we want to go one way or the other is still in the open.
This is good to hear. Another consideration is performance for how PHP is used. For usage where PHP is loaded once and used for a relatively long period of time (as in mod_php?), releasing a very lean core PHP and dynamically loading extensions is perfectly reasonable. The runtime cost of loading the extensions is amortized over a large number of requests. For usage where PHP is loaded often (as in CGI usage) the cost to load the extensions seperately can be have a much larger impact. In this case you want to think about building in all the often used extensions. -- Preston L. Bannister http://members.cox.net/preston.bannister/ pbannister on Yahoo Messenger -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
