Re: php4 + postgresql

[alex avriette <alex@posixnap.net>]

> 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).

I offered to send an Ultra 1 to Margarida, but when I found out what 
the shipping to Spain was, that was nixed. You can get an Ultra 1 
yourself for $65 if you're so inclined, talk to my pal John Butler at 
anysystem.com. It is reasonably fast (certainly fast enough to compile 
php all day long), and has enough room for ram, disk and other goodies. 
Although I have no idea why you need physical access to a machine to 
port php.

> 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?)

That would be silly. Fix the port. The PHP folks acknowledge it is 
broken (4.3.1) on 64-bit machines. This is fixed in their 
stable-current (what awful nomenclature) tree. I downloaded 
php4-STABLE-200305082130 today, and except for the sha1.c problem 
(using -O vs -O2), it compiled beautifully, and I have it running in 
the apache chroot jail right now. This strikes me as very easy to fix 
in the makefile, with the exception of having to move to the 
stable-current branch. Maybe you should ping wez@php.net about this.

>> 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.

Pardon me, I was unclear. I didn't mean to insinuate that there was a 
problem with propolice and php.

> as for chrooted httpd, php in 3.3 works pretty well with it,

(if you can compile it)

> but needs some manual effort (setup /var/www/tmp, move pear libs
> into the right place, etc).

I'm not familiar enough with php to understand why pear needs to be in 
/var/www, but I think some of these things could be done pretty easily. 
I seem to recall a couple of ports that come up with one of those text 
boxes and say "now run yada yada script to finish the install" (or in 
the case of shells, "edit /etc/shells yada yada"). What is so hard 
about this?

> 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).

Let me get this straight. The 3.4 port is working but the 3.3-current 
one has issues?

> 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 ...

I'm not familiar with the restart problem you're talking about here. 
Did I miss something?

Alex