Re: libxml bundling
| From: | Dan Kalowsky | Date: | Sat, 01 Jun 2002 20:21:33 +0000 |
| Subject: | Re: libxml bundling | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-84669@lists.php.net to get a copy of this message | ||
On Sat, 1 Jun 2002, Zeev Suraski wrote:
> I believe there's at least one company that effectively proved that the
> opposite is true, there are probably many others. I don't see a problem in
> having core technologies enabled by default. Purists can turn them off,
> but there are a hell of a lot more average users than there are purists.
I don't have the time right now to fully organize my thoughts on this and
many of the other emails so you'll have to wait for my response (I know I
know).
When I state that things shouldn't be enabled by default, it is not
towards making it harder for beginners. I would much rather see PHP using
something like:
./configure --basic
or
./configure --standard
or some variation along that theme.
Where whatever options are considered by the PHP development community as
essential can be enabled. A ./configure should really just build a basic
vanilla PHP in my mind. But this concept also goes against 6+ years of
configure scripts, and I realize it's an uphill battle. I know it annoyed
me to no end that MySQL was being built automatically when I first started
using PHP.
Or maybe the opposite of this should be allowed. A --disable-standard
flag that will turn off all the options PHP developers believe are
essential, but can then be overloaded with other options.
I have no idea if it is technically feasible, but it's an eventual
direction I would rather see. Finding what is enabled by default right
now is too difficult, and we just keep plugging in more.
>---------------------------------------------------------------<
Dan Kalowsky "The record shows, I took the blows.
http://www.deadmime.org/~dank And did it my way."
dank@nospam-deadmime.org - "My Way", Frank Sinatra
kalowsky@nospam-php.net