Re: PHP roadmap

> On Sat, 9 Sep 2000, Stig S. Bakken wrote: > > >PHP is a huge package, we have way over 100 PHP-specific configure > >options! I can think of three actions that could improve this situation; > >1: start rolling out binary distributions (RPMs, Debian packages, FreeBSD > >packages, Solaris packages...) for every release, 2: stop distributing all > >the extensions in the world with PHP, and make them available through PEAR > >instead, 3: make a more userfriendly/simple interface to configure. > > 2. and 3. makes sense.. 1. would just cause more trouble and work. > > >| One major problem is that there are these extensions > >| enabled by default: > >| > >| - GD > >| - MySQL > >| - XML > >| > >| Which, IMO, all should be enabled ONLY when wanted. > > > >Well, the MySQL and XML libs are bundled with PHP now, and should cause > >little problems now, especially for DSO builds. GD is trickier though, > > The bundled mysql causes much trouble..especially when there are other > modules in apache which use mysql. IMO bundled libs are bad thing (tm). > And enabling something by default is a very bad thing (tm) =). > I don't think bundled libraries or that enabling extensions are a bad thing. I think it is very helpful to have the expat libs bundled with PHP and enabled by default. It allows me to write more portable applications... The same goes for the WDDX functions and the Session functions. I do think that enabling and bundling the *wrong* libraries is a bad thing. The trouble is finding out which libraries are the wrong libraries. Personally, I disagree with the choice of bundling and enabling MySQL with PHP (the same goes with enabling GD), however, I'm sure there are other people who find it beneficial (just like I find having xml enabled by default beneficial). I thiink its all a matter of choosing the right extensions to enable by default, no one will agree with all these choices, however, the net result of enabling and bundling certain extensions is in my opinion positive. Sterling