From owner-freebsd-questions@FreeBSD.ORG Mon Sep 20 16:38:42 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4BB5106566B for ; Mon, 20 Sep 2010 16:38:42 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 684398FC12 for ; Mon, 20 Sep 2010 16:38:42 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OxjO5-0001aJ-Li for freebsd-questions@freebsd.org; Mon, 20 Sep 2010 18:38:41 +0200 Received: from pool-173-79-86-179.washdc.fios.verizon.net ([173.79.86.179]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Sep 2010 18:38:41 +0200 Received: from nightrecon by pool-173-79-86-179.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Sep 2010 18:38:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Mon, 20 Sep 2010 12:40:50 -0400 Lines: 49 Message-ID: References: <20100918114500.C20F41065761@hub.freebsd.org> <20100919194813.J11124@sola.nimnet.asn.au> <4C971132.7060809@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: pool-173-79-86-179.washdc.fios.verizon.net Subject: Re: why is the PHP stuff line "off" by default in ports/lang/php5? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2010 16:38:43 -0000 doug@safeport.com wrote: > On Mon, 20 Sep 2010, Rob Farmer wrote: > >> On Mon, Sep 20, 2010 at 00:45, Alex Dupre wrote: >>> This "issue" has been discussed too many times. The answer is simply >>> "no", but you can search the archives for the actual reason. You have to >>> comile the module for your specific apache installation. [snip] Many admins choose FastCGI over mod_php. We are not interested in having mod_php installed for us by default. So defaulting to 'off' is good. Had the OP been paying attention to this it would have been so simple for him to click the box in make config and build/install mod_php. Why should it be automatically "On" for those of us who do not want nor use mod_php? Being caught out when a change occurs is simply inattention to detail. [snip] > 4) My own opinion of best admin practices generally follows, if you > don't > need it, don't install it. > > If you build/install something like wordpress that requires both php and > apache, the correct thing is done. Usually even the required directives > are added to httpd.conf. The original question does not say if a port > management system was used to upgrade apache. If that was the case, > perhaps one could argue apache was not updated properly. Even in that > case, I would argue that the bug [if any] lies with the port management > system. The reason for paying attention is time can, and does, bring change. Maybe once upon a time installing mod_php was the default, but as more people selected alternatives it was decided to leave the choice up to the user. It is by not paying attention that such a change occurs and goes unnoticed. Blindly assuming that 'because it was always *this* way for years' does not mean things won't ever change. Many of these changes are logged in UPDATING. I have been updating Apache and PHP with portupgrade for years. I also recognize that a change in port build options may render the saved options file under the corresponding port directory in /var/db/ports invalid. When and if such a thing occurs it is up to me to recognize and adjust, rather than just blindly 'assume and ignore...'. These are the very typical duties of a system administrator. -Mike