From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new eclass: meson.eclass for the meson build system
Date: Thu, 4 May 2017 10:32:28 +0200 [thread overview]
Message-ID: <22794.59164.203668.872074@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20170504031143.GA16993@linux1>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
>>>>> 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 #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2017-05-04 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 3:11 [gentoo-dev] new eclass: meson.eclass for the meson build system William Hubbs
2017-05-04 6:07 ` Michał Górny
2017-05-04 8:32 ` Ulrich Mueller [this message]
2017-05-04 12:21 ` Ilya Tumaykin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22794.59164.203668.872074@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox