From: "Michał Górny" <mgorny@gentoo.org>
To: Dirkjan Ochtman <djc@gentoo.org>
Cc: "Gentoo Development" <gentoo-dev@lists.gentoo.org>,
"Manuel Rüger" <mrueg@gentoo.org>,
"Johan Bergström" <bugs@bergstroem.nu>
Subject: Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM
Date: Mon, 8 Feb 2016 22:41:19 +0100 [thread overview]
Message-ID: <20160208224119.14a513e1.mgorny@gentoo.org> (raw)
In-Reply-To: <CAKmKYaBvnc_PZ9i5CM5HRQ5=fOb3KsFaR1=QKtJh0MoP3Abmwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Thu, 4 Feb 2016 13:01:25 +0100
Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Thu, Feb 4, 2016 at 11:27 AM, Jason Zaman <perfinion@gentoo.org> wrote:
> > 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"
Well, the real issue here is that people are using USE_EXPAND as some
kind of 'here, upstream give us some grouped options, let's
thoughtlessly expose them all in some fancy USE_EXPAND without thinking
about usability of the solution!'
Of course, some of those flags make sense as USE flags. Some don't.
There are things that you practically always will want enabled. There
are things that should be controlled by global USE flags but instead
land in some custom USE_EXPAND because... because we can group it with
15 mildly relevant options!
So I have USE=zlib enabled because I want gzip support. But no, for
nginx I have to look through USE descriptions and find it's actually
nginx_modules_http_gzip because it happens that it is realized using
a loadable module!
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2016-02-08 21:41 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 [this message]
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=20160208224119.14a513e1.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=bugs@bergstroem.nu \
--cc=djc@gentoo.org \
--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