| 1 |
On 01/23/2016 07:26 AM, Aaron W. Swenson wrote: |
| 2 |
> In regards to: |
| 3 |
> https://archives.gentoo.org/gentoo-dev/message/877bee2af740e50e88f65cfe76126c0f |
| 4 |
> |
| 5 |
> I'm planning on introducing a new eclass to the tree and am also |
| 6 |
> considering adding a new USE_EXPAND as well that would control the |
| 7 |
> specific slots the user would like to build PostgreSQL-related |
| 8 |
> extensions against. |
| 9 |
> |
| 10 |
> Any objections? |
| 11 |
> |
| 12 |
|
| 13 |
There are three other USE_EXPAND with a similar aim: |
| 14 |
|
| 15 |
* PHP_TARGETS |
| 16 |
* PYTHON_TARGETS |
| 17 |
* RUBY_TARGETS |
| 18 |
|
| 19 |
And the related, |
| 20 |
|
| 21 |
* QEMU_SOFTMMU_TARGETS |
| 22 |
* QEMU_USER_TARGETS |
| 23 |
|
| 24 |
If the "_TARGETS" suffix isn't somehow wrong in this context, having it |
| 25 |
might act as a little bit of documentation for users who are used to the |
| 26 |
variables above. |
Archives