From: Jason Zaman <perfinion@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Manuel Rüger" <mrueg@gentoo.org>,
"Johan Bergström" <bugs@bergstroem.nu>
Subject: Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM
Date: Thu, 4 Feb 2016 18:27:40 +0800 [thread overview]
Message-ID: <20160204102740.GA26130@meriadoc> (raw)
In-Reply-To: <CAKmKYaC4ZrPeZH0zjsa_n-Gyz7c=-oVM1u7hOF5ZFaBMZsOa3Q@mail.gmail.com>
On Thu, Feb 04, 2016 at 11:03:27AM +0100, Dirkjan Ochtman wrote:
> On Wed, Feb 3, 2016 at 11:48 PM, Michał Górny <mgorny@gentoo.org> wrote:
> > Could we please finally stop introducing global USE flags that are
> > going to only be used by a single package? make.conf already looks like
> > random mix of randoms these days, with some extra random cruft being
> > added every second Tuesday.
>
> This is an interesting point, which I hadn't thought much about.
>
> It seems USE_EXPAND is really popular. What does it bring that has all
> these advantages over normal USE flags? It seems like APACHE2_MPMS,
> APACHE2_MODULES and CURL_SSL could just be normal USE flags with some
> REQUIRED_USE stuff.
>
> Actually, I'm not really sure I understand why we can't use normal USE
> flags for CPU_FLAGS_X86 or PYTHON_TARGETS, either.
Which looks easier and nicer to you?
NGINX_MODULES_HTTP="access auth_basic autoindex browser charset
fancyindex fastcgi geo gzip limit_req limit_zone map memcached proxy
realip referer rewrite scgi spdy split_clients ssi upstream_check
upstream_ip_hash userid uwsgi"
or:
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
What is the problem with global flags? Its namespaced and never going to
interfere with other packages. The only difference is the descriptions
are in use.desc instead of use.local.desc, why does that matter?
-- Jason
next prev parent reply other threads:[~2016-02-04 10:28 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 [this message]
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
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=20160204102740.GA26130@meriadoc \
--to=perfinion@gentoo.org \
--cc=bugs@bergstroem.nu \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mrueg@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