Re: php4 + postgresql

[Anil Madhavapeddy <anil@recoil.org>]

On Thu, May 08, 2003 at 06:53:25PM -0400, alex avriette wrote:
> 
> Yeah. This has been a recurring problem with both the PHP crowd and the 
> OpenBSD crowd. One doesn't support 64-bitness, the other doesn't care 
> what hardware or software you're using as long as their machine works.

Well, give me a sparc64, and I'll make php work on it.  sorry,
i cant fix bugs on architectures I dont have access to (and no,
an account doesnt count).

> Well, and you sent in a bug report. I figure if enough people write in 
> a bug report, somebody will notice and patch something. I'm not 
> familiar enough with ports myself, but the dropping of -O2 (for lha1.c) 
> would be real easy, as would running a newer flavor of php in the port.

It's already fixed in -current for about a week.  I'm tempted to mark
the PHP port broken on sparc64 since there have been so many clear
breakage reports on it (anyone using it successfully?)

> There was mention in the bug report you sent in that they were trying 
> to make the ports with chrooted httpd and propolice more friendly, I 
> guess more work needs to be done. Still, with a bug report sent in and 
> an easy fix, you'd think somebody could make the patch.

the ports are perfectly propolice friendly in 3.3; there's nothing
in the bug report that mentions it.  as for chrooted httpd, php
in 3.3 works pretty well with it, but needs some manual effort
(setup /var/www/tmp, move pear libs into the right place, etc).

In 3.4, a bunch of the work will already be done (pear installs
under the chroot, sets up the php include path correctly so it
work in both the chroot/non-chroot automatically). 

Im still not sure how to solve the restart problem.  The fix is
not "easy".  If it is, feel free to send in this patch that you
expect someone else to write ...

Anil