public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gordon Pettey <petteyg359@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM
Date: Thu, 4 Feb 2016 16:35:44 -0600	[thread overview]
Message-ID: <CAHY5MedFp1z9q1PGDPxOVHxDpuFTiHkOFmMhdGtdko8zXCCfEw@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFBpZ-zQ1Ojb+Rbr79a_NXZ4P5ppgE8T-tpEDw1Lmoa5ag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

On Thu, Feb 4, 2016 at 6:17 AM, Kent Fredric <kentfredric@gmail.com> wrote:

> On 4 February 2016 at 23:27, Jason Zaman <perfinion@gentoo.org> wrote:
> >
> > www-servers/nginx nginx_modules_http_access
> nginx_modules_http_auth_basic nginx_modules_http_autoindex
> nginx_modules_http_browser nginx_modules_http_charset
> nginx_modules_http_fancyindex nginx_modules_http_fastcgi
> nginx_modules_http_geo nginx_modules_http_gzip nginx_modules_http_limit_req
> nginx_modules_http_limit_zone nginx_modules_http_map
> nginx_modules_http_memcached nginx_modules_http_proxy
> nginx_modules_http_realip nginx_modules_http_referer
> nginx_modules_http_rewrite nginx_modules_http_scgi nginx_modules_http_spdy
> nginx_modules_http_split_clients nginx_modules_http_ssi
> nginx_modules_http_upstream_check nginx_modules_http_upstream_ip_hash
> nginx_modules_http_userid nginx_modules_http_uwsgi
>
>
> I used to do this sort of thing for the PYTHON_TARGETS stuff, but it
> hurts way too badly.
>
> So now instead I have a couple of convenience tools in `package.env` +
> `env.d` instead. ( Queue many ewing )
>
> Its really sad we can't just have what Paludis does, package.use side
> support for USE_EXPAND.
>
> www-servers/nginx  normal_use_flags NGINX_MODULES: http_access
> http_auth_basic http_autoindex
>
> Or similar.
>

But we can do exactly that, as of at least portage-2.2.24, possibly earlier.

[-- Attachment #2: Type: text/html, Size: 1824 bytes --]

  reply	other threads:[~2016-02-04 22:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 22:29 [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM Manuel Rüger
2016-02-03 22:48 ` Michał Górny
2016-02-04 10:03   ` Dirkjan Ochtman
2016-02-04 10:27     ` Jason Zaman
2016-02-04 12:01       ` Dirkjan Ochtman
2016-02-04 12:22         ` Alexis Ballier
2016-02-08 21:41         ` Michał Górny
2016-02-08 22:34           ` Kent Fredric
2016-02-08 22:44             ` James Le Cuirot
2016-02-08 22:56               ` Kent Fredric
2016-02-08 22:59             ` Luis Ressel
2016-02-08 23:22               ` Kent Fredric
2016-02-08 23:33                 ` Luis Ressel
2016-02-09  6:37               ` Patrick Lauer
2016-02-09  8:18                 ` Luis Ressel
2016-02-08 23:07             ` Luis Ressel
2016-02-04 12:17       ` Kent Fredric
2016-02-04 22:35         ` Gordon Pettey [this message]
2016-02-05  6:38           ` Jason Zaman
2016-02-05 11:07             ` Michał Górny
2016-02-06 20:08               ` Matt Turner
2016-02-04 10:14   ` Alexis Ballier

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=CAHY5MedFp1z9q1PGDPxOVHxDpuFTiHkOFmMhdGtdko8zXCCfEw@mail.gmail.com \
    --to=petteyg359@gmail.com \
    --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