From owner-freebsd-questions@FreeBSD.ORG Mon Mar 31 21:43:08 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9997D37B401 for ; Mon, 31 Mar 2003 21:43:08 -0800 (PST) Received: from alpsgiken.alpsgiken.gr.jp (www.alpsgiken.gr.jp [210.166.150.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 820F643F85 for ; Mon, 31 Mar 2003 21:43:07 -0800 (PST) (envelope-from joel@alpsgiken.alpsgiken.gr.jp) Received: from zz_radiant2 (www1.alpsgiken.gr.jp [61.114.244.165]) by alpsgiken.alpsgiken.gr.jp (8.9.1a/3.7W) with ESMTP id OAA15933 for ; Tue, 1 Apr 2003 14:43:05 +0900 Date: Tue, 01 Apr 2003 14:47:50 +0900 From: Joel Rees To: freebsd-questions@freebsd.org Message-Id: <20030401141621.F8EA.JOEL@alpsgiken.gr.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.00.11 Subject: php, mod_php unifiable? Pear? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 05:43:08 -0000 First question: Does everyone keep mod_php4 and php4 as separate ports, even when using both. I'm assuming, since the php.standalone (or whatever it was) is there and contains it's own php.ini, that is the case. Does anyone try to keep them together? (I can see, since I want postgresql to talk to php for web apps and I may not want that for the command-line php, that it might be reasonable to keep them separate. But my first inclination is to keep them together.) Second question: Does everyone just keep pear where it gets loaded automatically under /usr/ports/lang/php4/work/php-4.2.3/pear and /usr/ports/www/mod_php4/work/php-4.2.3/pear (or wherever those were)? I'm asking these questions particularly in light of the go_pear script preferring to load pear under /usr/local/share/pear, and expecting php to be in /usr/local/share, as well. -- Joel Rees