Re: libxml bundling
| From: | Zeev Suraski | Date: | Thu, 08 May 2003 15:48:41 +0000 |
| Subject: | Re: libxml bundling | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-1392@lists.php.net to get a copy of this message | ||
At 18:16 08/05/2003, Sascha Schumann wrote:
is, IMHO, the wrong way to think about it. Requiring the sysadmin to read
docs, bump into configure errors, install/configure additional libraries,
does not fall in the category of being helpful or easy.
Right, it falls into his job description. I don't think
sysadmins would like it, if you would make their jobs
obselete.
Bundling libxml would make sysadmin's jobs obsolete? If that was such a huge idea, Sterling and I would have kept it to ourselves and become millionaires :)
With that rationale, why not throw in additional quirks and problems into the PHP setup, so that they have more work to do?
Building plain vanilla PHP should be trivial, requiring as little of the abovementioned sysadmin tasks as possible.
The obvious question that comes to mind is "where do we draw the
line?" IMHO, XML is such a basic requirement that this particular case is
a no brainer.
Right, that's why already bundle expat: You don't need any
external libraries to handle XML.
The working assumption for this entire discussion is that expat is insufficient for this day and age, and should be replaced with libxml.
Zeev