From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Call for 7.5 feature completion |
Date: | 2004-05-18 21:49:43 |
Message-ID: | 200405182349.43177.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> Of course not, but I still don't see your point. plPHP doesn't need
> PHP+PostgreSQL support. Nor does PHP+PostgreSQL conflict with using
> plPHP...
>
> PHP doesn't even need to be installed for plPHP to work... You just
> need the source tree for building.
I don't talk about manual build processes, I talk about (semi-)automatic
package builds. The PHP package has a build dependency on PostgreSQL,
because it needs libpq. So PostgreSQL needs to be built and installed
before PHP can be built. But then, if PL/PHP were to be integrated
into PostgreSQL, PHP needs to be installed first, so the
PostgreSQL+PL/PHP build can get at the PHP headers files and whatever
else it needs. So you can neither build PHP first nor build PostgreSQL
first.
So building PL/PHP doesn't need a PHP with PostgreSQL support. But no
one is going to build two versions of PHP packages just so PostgreSQL
can build. That is a mess we can happily avoid.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2004-05-18 22:14:48 | Re: add server include files to default installation? |
Previous Message | Bruce Momjian | 2004-05-18 21:47:24 | Re: Relocatable installs |