Date: Sun, 10 Jun 2007 09:31:33 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Christopher Hilton <chris@vindaloo.com> Cc: Jonathan Horne <freebsd@dfwlp.com>, bob@a1poweruser.com, User Questions <freebsd-questions@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Php5 port and Apache Module Message-ID: <466BA8D5.9090009@quip.cz> In-Reply-To: <466B579F.2080106@vindaloo.com> References: <NBECLJEKGLBKHHFFANMBIEGGCDAA.bob@a1poweruser.com> <466B17E6.9000906@vindaloo.com> <49217.192.168.125.81.1181426436.squirrel@webmail.dfwlp.org> <466B579F.2080106@vindaloo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Christopher Hilton wrote: > Jonathan Horne wrote: [...] > > Everyone seems to be misunderstanding my question. I'm aware of how to > build mod_php5. I'm curious about why the default configuration builds > php5 as a standalone CLI and CGI rather than as an apache module. I'm > assuming that there is some good engineering behind this decision but > I'd like to know a little more about that engineering. Is there some > advantage to running php as a Fast CGI process? I guess that mod_php5 depends on Apache and maintainer don't want this big dependency. The second is - if it will depends on Apache of some version (eg. 1.3) it will be broken with another version (2.0 and 2.2). It apply for binary packages. If somebody is compiling ports himself, then can check option "with apache" or add WITH_APACHE in to /etc/make.conf Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?466BA8D5.9090009>