[gentoo-dev] New USE_EXPAND: POSTGRES

2016-01-23 Thread Aaron W. Swenson
In regards to:
https://archives.gentoo.org/gentoo-dev/message/877bee2af740e50e88f65cfe76126c0f

I'm planning on introducing a new eclass to the tree and am also
considering adding a new USE_EXPAND as well that would control the
specific slots the user would like to build PostgreSQL-related
extensions against.

Any objections?


signature.asc
Description: Digital signature


Re: [gentoo-dev] New USE_EXPAND: POSTGRES

2016-01-23 Thread Aaron W. Swenson
On 2016-01-23 09:48, Michael Orlitzky wrote:
> On 01/23/2016 07:26 AM, Aaron W. Swenson wrote:
> > In regards to:
> > https://archives.gentoo.org/gentoo-dev/message/877bee2af740e50e88f65cfe76126c0f
> > 
> > I'm planning on introducing a new eclass to the tree and am also
> > considering adding a new USE_EXPAND as well that would control the
> > specific slots the user would like to build PostgreSQL-related
> > extensions against.
> > 
> > Any objections?
> > 
> 
> There are three other USE_EXPAND with a similar aim:
> 
>   * PHP_TARGETS
>   * PYTHON_TARGETS
>   * RUBY_TARGETS
> 
> And the related,
> 
>   * QEMU_SOFTMMU_TARGETS
>   * QEMU_USER_TARGETS
> 
> If the "_TARGETS" suffix isn't somehow wrong in this context, having it
> might act as a little bit of documentation for users who are used to the
> variables above.

Good point.

POSTGRES_TARGETS it is.

Any objections or comments to that?


signature.asc
Description: Digital signature


Re: [gentoo-dev] New USE_EXPAND: POSTGRES

2016-01-23 Thread Michael Orlitzky
On 01/23/2016 07:26 AM, Aaron W. Swenson wrote:
> In regards to:
> https://archives.gentoo.org/gentoo-dev/message/877bee2af740e50e88f65cfe76126c0f
> 
> I'm planning on introducing a new eclass to the tree and am also
> considering adding a new USE_EXPAND as well that would control the
> specific slots the user would like to build PostgreSQL-related
> extensions against.
> 
> Any objections?
> 

There are three other USE_EXPAND with a similar aim:

  * PHP_TARGETS
  * PYTHON_TARGETS
  * RUBY_TARGETS

And the related,

  * QEMU_SOFTMMU_TARGETS
  * QEMU_USER_TARGETS

If the "_TARGETS" suffix isn't somehow wrong in this context, having it
might act as a little bit of documentation for users who are used to the
variables above.