From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] php-ext-source-r3 eclass improvements
Date: Mon, 29 Jan 2018 08:50:27 -0500 [thread overview]
Message-ID: <48afe4ae-8f68-aff9-2c2e-f9b39a55c982@gentoo.org> (raw)
In-Reply-To: <20180126153857.30315-1-grknight@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 458 bytes --]
On 1/26/2018 10:38 AM, Brian Evans wrote:
> The following patches improve the php-ext-source-r3 eclass by introducing
> two new variables.
>
> The first allows the configration INI name to vary from a hard-coded default
> of the module name.
>
> The second allows USE dependencies to be added to each implementation
> similar to python team's PYTHON_REQ_USE.
>
> Comments are welcome
>
> Brian
>
>
These are now committed.
Brian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-01-29 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 15:38 [gentoo-dev] [RFC] php-ext-source-r3 eclass improvements Brian Evans
2018-01-26 15:38 ` [gentoo-dev] [PATCH 1/2] php-ext-source-r3.eclass: Introduce PHP_INI_NAME variable Brian Evans
2018-01-26 15:38 ` [gentoo-dev] [PATCH 2/2] php-ext-source-r3.eclass: Introduce PHP_EXT_NEEDED_USE Brian Evans
2018-01-29 13:50 ` Brian Evans [this message]
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=48afe4ae-8f68-aff9-2c2e-f9b39a55c982@gentoo.org \
--to=grknight@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