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