Re: How do I depend on a flavoured PHP port? The Handbook is wrong??

From: Harry Schmalzbauer <>
Date: Sun, 12 Sep 2021 12:56:47 UTC
Am 07.09.2021 um 04:15 schrieb Mel Pilgrim:
> On 2021-09-06 17:35, Tatsuki Makino wrote:
>> Mel Pilgrim wrote on 2021/09/04 09:36:
>>> I'm trying to add a dependency on a flavoured PHP application, but 
>>> the Porter's Handbook (section 7.3.1) instructions don't work.  It 
>>> says to just add "@${PHP_FLAVOR}" but that's an empty variable.
>>> I can't add php:flavors to the USES line because that then requires 
>>> this port be flavoured as if it were itself a PHP application (it's 
>>> not, it's just a metaport).
>>> Adding "php" to USES works, but adds an unnecessary lang/php?? 
>>> dependency.
>>> What I need is the PHP counterpart to python:env, but I can't seem 
>>> to find it?
>> The RUN_DEPENDS+= near line 271 of Mk/Uses/ seems to always be 
>> executed.
>> It would be an excessive dependency if PHP was used as a script just 
>> for building.
>> That's what this is about, isn't it? :)
> It's for a metaport that wants to add a flavored PHP port to 
> RUN_DEPENDS; but yes, needing PHP as a BUILD_DEPEND would probably be 
> another example.

I can't remember if this still is undocumented... and if I already 
reported that this is missing to be documented.
Also can't remember where I found that it can look like this, most 
likely underneith ports/Mk:

RUN_DEPENDS=    git:${PORTSDIR}/devel/git@tiny

It's from one of my local meta-ports.

As far as I remember, it worked as intended.