Jeremy Chadwick wrote:
> On Tue, Mar 14, 2006 at 01:57:21PM +0100, Uro? Gruber wrote:
>> If this is right
>> portsdb -r www/php5-cgi
>> then no other ports depend on php5 cgi mode. Because of that I thing
>> it's ok if cgi version is installed in
>> /usr/local/bin/phpX-cgi etc and php-cgi.ini
>> This does not break any port and install is easy and automatic.
>> Is this possible to change in ports by maintainer, because I don't quite
>> understand how is done installing of binaries.
> I maintain the port which explicitly relies on the CGI version of PHP.
> It's called suphp. I use the WANT_PHP_CGI knob, as defined in
> ports/Mk/bsd.php.mk. There are a total of four (4) ports which use
> WANT_PHP_CGI, and 3 of the 4 only use it when suphp support is
> The number of Emails I get per week about the suphp port (particularly
> "why hasn't it been updated to 0.6.x") proves to me how many FreeBSD
> server administrators rely on it. suphp is presently only one of two
> methods available for securely running PHP scripts as the script owner
> or per a user/group directive inside of an Apache <VirtualHost> block.
> It's a important port for web hosting providers.
> Please be aware of this before requesting/submitting any changes.
> Ensure your changes work with suphp -- thoroughly -- before agreeing
> they be committed.
Ok my mistake. I looks like portupgrade did not recognize this one. Btw.
I have cgi with per user virtualhost
without suphp and it works.
As I said before. I'm not good at port scripting so I'm waiting for port
maintainer to reply so we can all talk about