I think it could be a good idea to have the USE flag to enable plphp use in postgresql ebuild: http://plphp.commandprompt.com/ Thanks
Hmm, I tested it. The problem is that PL/PHP is broken on threading-enabled PHP, as seen on the mailinglist: http://hosting.commandprompt.com/pipermail/plphp/2006-July/000340.html
The software in question has not been updated since 2007, is only documented to work with PostgreSQL 8.1, which is no longer in Portage, and this bug has not been updated in over 5 years. If this were to be added, it might better fit as a separate ebuild or in an overlay, anyway. I suggest that this bug be closed as OBSOLETE.
(In reply to comment #2) > The software in question has not been updated since 2007, is only documented to > work with PostgreSQL 8.1, which is no longer in Portage, and this bug has not > been updated in over 5 years. > > If this were to be added, it might better fit as a separate ebuild or in an > overlay, anyway. > > I suggest that this bug be closed as OBSOLETE. Just as I was about to do that six months or so ago I discovered they had updated PL/PHP. https://public.commandprompt.com/projects/plphp/files It looks like the highest documented version it works with 9.0, but 9.1 was only released a couple months ago. I'm currently working on an eclass that will allow us to install this on several major versions rather than just one.
Apparently the upstream authors can't or won't keep up with PostgreSQL. PL/PHP will not be included with the PostgreSQL ebuilds.