On Aug 4, 2014, at 23:15 , Melvyn Sopacua wrote:
> So, there is no php-cgi or fpm, but www/mod_php5 is not in phpMyAdmin's
> dependencies, which means WANT_PHP_WEB is not satisfied, yet no errors
> are generated.
While it looks like that’s the expected behaviour right now, I don’t agree that
i
Hi Matthew,
On Mon, 4 Aug 2014, Matthew Pounsett wrote:
As far as I can tell, the only way you get an installed version of PHP
without either the CGI or FPM options set is to install mod_php5.
That makes installing mod_php5 a prerequisite to making mod_php5 a
dependency to any port that uses W
On Aug 3, 2014, at 12:29 , Melvyn Sopacua wrote:
> Hi Matthew,
>
> On Sun, 3 Aug 2014, Matthew Pounsett wrote:
>
>> On Aug 3, 2014, at 02:07 , Melvyn Sopacua wrote:
>
>>> For automated builds use the OPTIONS framework. Tinderbox can handle
>>> that just fine.
>>
>> Right, and I’m speaking f
On Aug 4, 2014, at 09:05 , Alex Dupre wrote:
> 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,
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
Hi Matthew,
On Sun, 3 Aug 2014, Matthew Pounsett wrote:
On Aug 3, 2014, at 02:07 , Melvyn Sopacua wrote:
For automated builds use the OPTIONS framework. Tinderbox can handle
that just fine.
Right, and I’m speaking from the perspective of the admin building the
port, not the maintainer. T
On Aug 3, 2014, at 02:07 , Melvyn Sopacua wrote:
>
> I don't see the problem.
> If you want the mod_php module in your port set WANT_PHP_MOD.
> If you don't care which implementation it is as long as it can speak
> with a webserver, you set WANT_PHP_WEB.
>
> The WANT_PHP_WEB knob is for >port
Hello!
On Sat, 2 Aug 2014, Matthew Pounsett wrote:
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 envir
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
