From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: build/install xml2 when configured with libxml |
Date: | 2007-04-14 15:48:10 |
Message-ID: | 4488.1176565690@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Peter Eisentraut wrote:
>> But the policy is that the presence of features in the final build
>> should not depend on the incidental presence of features in the build
>> environment. Either you select a feature, then it's built, or you
>> don't, then it's not. So the only options we really have are adding
>> another switch for libxslt, or including it with libxml. I'm not sure
>> which is better.
> Then let's add a switch for libxslt.
+1 --- the fact that so many buildfarm members only have one of the two
libraries is pretty suggestive that that's common. We shouldn't require
both libraries to build the core xml features, if only because
contrib/xml2 is expected to go away eventually, no?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-04-14 15:49:31 | Re: Table function support |
Previous Message | Andrew Dunstan | 2007-04-14 13:12:10 | Re: build/install xml2 when configured with libxml |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-04-14 15:49:31 | Re: Table function support |
Previous Message | Andrew Dunstan | 2007-04-14 13:12:10 | Re: build/install xml2 when configured with libxml |