Re: Re: cvs: php4 / acinclude.m4 configure.in /build build.mk /bundle/expat .cvsignore Changes README README.php ascii.h asciitab.h config.m4
expat.h iasciitab.h internal.h l
| From: | Jani Taskinen | Date: | Mon, 19 May 2003 22:36:24 +0000 |
| Subject: | Re: Re: cvs: php4 / acinclude.m4 configure.in /build build.mk /bundle/expat .cvsignore Changes README README.php ascii.h asciitab.h config.m4 expat.h iasciitab.h internal.h l |
||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-1745@lists.php.net to get a copy of this message | ||
On Mon, 19 May 2003, Andi Gutmans wrote:
>At 08:29 PM 5/19/2003 +0200, Derick Rethans wrote:
>>On Mon, 19 May 2003, Andi Gutmans wrote:
>>
>> > At 02:27 PM 5/19/2003 -0400, Joao Prado Maia wrote:
>> > >On Mon, 19 May 2003, Sebastian Bergmann wrote:
>> > >
>> > > > Adam Dickmeiss wrote:
>> > > > > Why? Jani is removing code, while at the same time make a better
>> > > > > product. He should be rewarded for this.
>> > > >
>> > > > It would have been better if had written a mail to this list
>> alongside
>> > > > his CVS commit.
>> > > >
>> > >
>> > >It was - see the huge thread 'Bundling libxml2 default?' on this list
>> > >for
>> > >the discussion.
>> >
>> > I just read it now and didn't see any definitive agreement on the subject.
>>
>>There wasn't any definitive agreement on bundling libxml either, so :)
>
>When there's no agreement then we usually stay with the Status Quo.
>
>>Anyway, we now require libxml2 for the moment, which should give us a
>>much more solid library to base our XML extensions on. And by unbundling
>>expat alongside with libxml we no longer say that expat is our prefered
>>library.
>
>I don't really care too much for expat and I'm not even sure if I wouldn't
>support removing it, but I do care that Jani just nukes stuff which has
>been in PHP for years from the CVS without reaching some kind of agreement
>on the subject.
Basically Sterling first nuked it. I just made it more convenient for
everyone (basically the consensus was not to bundle libxml).
We want better xml support and using expat for it is not an option.
And I'd rather see ext/xml, ext/wddx, and any other extension that relied
on the bundled expat to use 'native' libxml functions instead of this
compat.c stuff.
Just think of this as progress. (the eggs and omelette thing :)
--Jani