From dev-return-18698-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Sun Jul 29 15:14:32 2007 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 62075 invoked from network); 29 Jul 2007 15:14:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jul 2007 15:14:30 -0000 Received: (qmail 41205 invoked by uid 500); 29 Jul 2007 15:14:29 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 41139 invoked by uid 500); 29 Jul 2007 15:14:29 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 41128 invoked by uid 99); 29 Jul 2007 15:14:29 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jul 2007 08:14:29 -0700 X-ASF-Spam-Status: No, hits=1.6 required=10.0 tests=MISSING_HEADERS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [65.99.219.155] (HELO haxent.com) (65.99.219.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Jul 2007 15:14:23 +0000 Received: from karmic-2.local (unknown [201.21.162.101]) by haxent.com (Postfix) with ESMTP id A477F30858 for ; Sun, 29 Jul 2007 12:14:00 -0300 (BRT) Message-ID: <46ACAEB2.7060901@haxent.com.br> Date: Sun, 29 Jul 2007 12:13:54 -0300 From: Davi Arnaut MIME-Version: 1.0 Cc: dev@apr.apache.org Subject: Re: Get rid of builtin expat References: <46ACA060.1060402@haxent.com.br> <5c902b9e0707290758w67fe18e2hc7d2b43911b4ed09@mail.gmail.com> In-Reply-To: <5c902b9e0707290758w67fe18e2hc7d2b43911b4ed09@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Justin Erenkrantz wrote: > On 7/29/07, Davi Arnaut 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