Date: Mon, 04 Aug 2014 15:05:54 +0200 From: Alex Dupre <ale@FreeBSD.org> To: Matthew Pounsett <matt@conundrum.com>, freebsd-ports@freebsd.org Subject: Re: WANT_PHP_WEB is just a synonym for WANT_PHP_CGI in automated build environments Message-ID: <53DF8532.30506@FreeBSD.org> In-Reply-To: <F00B4361-E712-4E1D-B95F-E11C41BDA3C6@conundrum.com> References: <F00B4361-E712-4E1D-B95F-E11C41BDA3C6@conundrum.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Pounsett ha scritto:
>
> 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) – where *only* the direct dependencies of a port are installed at build time – there isn’t 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?
You missed the fact that you can install the php module as a separate
port/package together with the core php package. Not only, mod_php port
requires core php port, that is the one containing the cgi version. So
there isn't any problem with tinderbox/poudriere.
--
Alex Dupre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53DF8532.30506>