Falkon and specifying flavors when building

Falkon can be build in two flavors i.e. falkon and falkon-qtonly without akonadi.
How do you set the flavor qtonly in make.conf for building ?
I see only /usr/ports/www/falkon as port and not falkon-qtonly.
Some info,

Package flavors (<flavor>: <package>)
  • default: falkon
  • qtonly: falkon-qtonly
---------------------------------------------
I'll try to add a line to make.conf ?,
FLAVORS= falkon-qtonly
 
Will you please make an effort to post your questions in the right subforum? I always have to move your posts. This belongs in "Installation and Maintenance of Ports or Packages".
 
With that line added poudriere gives me,
Code:
Warning: (devel/py-six@qtonly): Error: Invalid FLAVOR 'qtonly' for devel/py-six
[00:00:07] Error: Fatal errors encountered gathering ports metadata
And dies in a hard way.

Flavors are a bad idea.
Can you set a flavor specific for one package, and not all packages I build?
Why is py-six pulled in?
Why does it care about a qtonly flavor ?
Grrr. :)
Can't I use ":" somewhere to bind a flavor to a port ?
 
Can you set a flavor specific for one package, and not all packages I build?
There's probably a simpler way these days but I can't remember how to do it. This is the old school way:
Code:
.if ${.CURDIR:M*/www/falkon}
  FLAVOR=qtonly
.endif

Why is py-six pulled in?
Most likely cause is because it's a dependency of a dependency.

Why does it care about a qtonly flavor ?
It doesn't. But because it's a python module it has it's own FLAVORS (py37, py38, etc) and qtonly isn't among those.
 
Code:
.if ${.CURDIR:M*/www/falkon}
  FLAVOR=qtonly
.endif
Seems to work.
It translates in the build to:
Code:
PACKAGE_BUILDING_FLAVORS=yes
MAKE_ARGS= FLAVOR=qtonly
 
Back
Top