From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgsql-advocacy] Increased company involvement |
Date: | 2005-05-03 18:40:50 |
Message-ID: | 20050503153829.O53065@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Tue, 3 May 2005, Andrew Dunstan wrote:
>
>
> Robert Treat wrote:
>
>> On Tuesday 03 May 2005 13:46, Andrew Dunstan wrote:
>>
>>> Robert Treat wrote:
>>>
>>>> Is telling the rpm maintainers to go fix their rpm's an option? As has
>>>> been hashed out before, the only thing that makes plphp different from
>>>> other pl's is that some of the current packagers are taking shortcuts
>>>> with the packaging scripts which introduces dependency issues. IMHO what
>>>> is included in the postgresql cvs and what is included in the main
>>>> tarball for postgresql should not be dictated by outside packagers.
>>>>
>>> That wasn't my understanding of the previous discussion. Does not php
>>> require pg client support configured in at build time?
>>>
>>>
>>
>> If your compiling it from source, it works similarly to perl... you only
>> need pg when compiling pg support into php, but you dont need tthis in for
>> plphp.
>
>
> I suspect you are missing the point completely.
>
> It is in fact not like building perl at all. I just downloaded php-4.3.11 and
> got this from configure --help:
>
> --with-pgsql[=DIR] Include PostgreSQL support. DIR is the PostgreSQL
> base install directory, defaults to
> /usr/local/pgsql.
>
> You will not find any such parameter for building perl.
>
> Now it is true that you don't need this in for plphp. But if you want php to
> have pg client support you need pg built first. And no sane packager is going
> to build php twice.
Actually, if you look through FreeBSD ports, this is exactly what happens
... when you build /usr/ports/devel/php4, it builds a "vanilla" php, no
modules ... if you want pgsql support, you go into
/usr/ports/databases/php4-pgsql, and build that (which has a dependency on
lang/php4) ...
So, for plphp, a "port" would just have to install /usr/ports/lang/php4 to
build, but would not necessarily build php4-pgsql ...
it is done this way to avoid packagers having to build a monolithich
"contains everything" php4 ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2005-05-03 18:43:41 | Re: [pgsql-advocacy] Increased company involvement |
Previous Message | Tom Copeland | 2005-05-03 18:40:27 | [OT] Re: [HACKERS] Increased company involvement |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-05-03 18:43:39 | Re: Bogus assertion in multixact.c? |
Previous Message | Tom Copeland | 2005-05-03 18:40:27 | [OT] Re: [HACKERS] Increased company involvement |