php-cli and php-cgi

Jeremy Chadwick freebsd at
Mon Mar 13 11:23:27 UTC 2006

On Mon, Mar 13, 2006 at 11:33:23AM +0100, Uro? Gruber wrote:
> I'm not being rude. I just pointed that I'm using cgi and cli (not mod 
> as he refer). I've read UPDATING
> and if you're talking about 2004 when port is split to php-extension 
> etc. I think this is not the case.


How does your solution (re: naming the PHP interpreter php-cli and
php-cgi, respectively) handle scripts and utilities which rely on
the existance of /usr/local/bin/php (or simply "php" in your path)?

The answer will probably be "a symlink".  Okay, which PHP binary do
you choose to symlink to?  php-cgi or php-cli?

I cannot tell you how many times I have seen on mailing lists for
PHP-related software, especially suphp, individuals asking why the
software didn't work -- only to find out they had installed the CLI
version of PHP, not the CGI version.

I do acknowledge that you can have both on a single system; there is
no denying that.  But /usr/local/bin/php has to be one or the other.
Presently, PHP doesn't offer a way for software or scripts (i.e.
GNU configure scripts) to determine which type is installed, as far
as I know...

This is probably one of many reasons why the CLI and CGI ports are

| Jeremy Chadwick                                 jdc at |
| Parodius Networking               |
| UNIX Systems Administrator                   Mountain View, CA, USA |
| Making life hard for others since 1977.                             |

More information about the freebsd-ports mailing list