Justin Erenkrantz wrote: > On 7/29/07, Davi Arnaut <[EMAIL PROTECTED]> wrote: >> Hi >> >> Can't we get rid of the builtin expat on trunk? Yesterday I had yet >> another problem linking python (python-xml) and a static build apr-util >> together on a pretty complex application. I know I should have linked >> apr-util with the system expat, but then what's the point of having one >> builtin? >> >> http://people.apache.org/~davi/apr-util-remove-expat.patch > > Because not everyone (hi Windows folks) has expat already installed. > For required dependencies, I'm in favor of bundling - and we used to > be ahead of expat releases - though that situation has changed in the > last 5 years or so. Regardless, if expat were optional, then I say we > could easily remove it; but apr_xml_* has been a mandatory API since > 1.0, so IMO we shouldn't remove it until we did an APR 2.x and make > apr_xml_* optional... -- justin
We don't need to bundle it because it's a mandatory API, we just have to explain to (win32) users how to extract a recent expat at xml/. It's not a matter of API and we don't *need* to bundle expat, it's becoming a burden. -- Davi Arnaut
