From owner-freebsd-ports@FreeBSD.ORG Sat Aug 2 21:38:27 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27BCAFF9 for ; Sat, 2 Aug 2014 21:38:27 +0000 (UTC) Received: from kaywinnit.conundrum.com (smtp.conundrum.com [IPv6:2001:4900:1:213::2:20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05A662157 for ; Sat, 2 Aug 2014 21:38:27 +0000 (UTC) Received: from [2001:4900:1044:0:e170:1984:1f06:1503] by kaywinnit.conundrum.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XDh0T-0007Cn-3c; Sat, 02 Aug 2014 21:38:25 +0000 From: Matthew Pounsett Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Sat, 2 Aug 2014 17:38:55 -0400 Subject: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments To: freebsd-ports@freebsd.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2014 21:38:27 -0000 It looks to me like the rules that WANT_PHP_WEB uses to decide whether = to build the CGI or module version of PHP will always choose the CGI = version unless the module is already installed. If this is true, it = means that in automated build environments (e.g. tinderbox) =96 where = *only* the direct dependencies of a port are installed at build time =96 = there isn=92t any way to tell WANT_PHP_WEB to install the module. This = effectively makes WANT_PHP_WEB a synonym for WANT_PHP_CGI in these = environments. Have I missed something, or is this a significant flaw in the design of = the WANT_PHP_{WEB,CGI,MOD} knobs? =20 It seems to me that this should be changed in one of three ways: 1) It should be possible to provide direction to WANT_PHP_WEB via some = make.conf knob 2) WANT_PHP_WEB should be removed, and WANT_PHP_{CGI,MOD} should always = be chosen using a radio selector at config time, or by setting in = make.conf 3) WANT_PHP_WEB should cause a radio button selector to appear at port = config time (3) seems like the least desirable, since it leaves no way to provide = direction in a batch mode build. I think my preference would be for = (2). Does anyone have any other ideas for how to improve this? Or any = pointers to a way that already exists to provide direction to the ports = system about whether WANT_PHP_WEB should imply _CGI or _MOD?