>>>>> On Wed, 3 May 2017, William Hubbs wrote:

> # @VARIABLE: mymesonargs

I guess this is modeled after cmake-utils.eclass, but should eclass
variables really use the "my" prefix? There seems to be no formal rule
for this, but numerous devmanual examples (like MY_PV) suggest that MY
is available for internal ebuild use.

So maybe mesonargs or emesonargs would be a better name here?

Ulrich

Attachment: pgpd8nphhqjQK.pgp
Description: PGP signature

Reply via email to