From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Robin Ericsson <robin(dot)ericsson(at)profecta(dot)se>, "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] plPHP in core? |
Date: | 2005-04-05 16:00:09 |
Message-ID: | 14098.1112716809@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> I understand your point Tom. However as I said in a earlier
> post, just because it is in core doesn't mean they have to
> package it.
If it were in our CVS, but still shipped as an separate, independently-built
source package, then my objection would not apply. However such a setup
seems to lose a lot of the synergy that is being claimed for having it
in our CVS. plPHP would then still have its own separate configure and
build process, and it wouldn't get tested "for free" in the same kind of
way that the current core PLs do.
Or were you trying to say "let's ship it, and I don't care if major
Linux distributors refuse to include it in their packaging because it's
too hard to build that way"? Somehow that doesn't seem to square with
the goal of making plPHP more available rather than less so.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-05 16:05:29 | Re: [HACKERS] plPHP in core? |
Previous Message | Hannes Dorbath | 2005-04-05 15:55:40 | Postmaster running out of discspace; Data corruption? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-05 16:05:29 | Re: [HACKERS] plPHP in core? |
Previous Message | tony | 2005-04-05 15:53:57 | Re: [HACKERS] plPHP in core? |