public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <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 13:01:25 +0100	[thread overview]
Message-ID: <CAKmKYaBvnc_PZ9i5CM5HRQ5=fOb3KsFaR1=QKtJh0MoP3Abmwg@mail.gmail.com> (raw)
In-Reply-To: <20160204102740.GA26130@meriadoc>

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"
>
> 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

Well, it seems like we could easily skip the _modules_http suffix, and
the difference would not nearly be so large.

The problem I have with it is that, as a user, it's yet another
concept to grasp and configure. Instead of just working with USE flags
(e.g. looking at use.desc or using ufed to review, configuring USE
flags in make.conf or package.use), I now have to find/learn a bunch
of new stuff. What packages use what USE_EXPAND things (e.g. apache
has two), what are valid values for all of these.

Where with simple USE flags, there is a single mechanism that I have
to learn and can apply across the board; with USE_EXPAND stuff, I have
to learn new stuff for each new package that adopts one or more
USE_EXPAND things.

So if this cosmetic expansion is the only advantage, that seems like a
relatively limited one (e.g. it could be improved a lot just by
formatting), and the trade-off of introducing all this extra
complexity doesn't make that much sense to me.

Cheers,

Dirkjan


  reply	other threads:[~2016-02-04 12:01 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 [this message]
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='CAKmKYaBvnc_PZ9i5CM5HRQ5=fOb3KsFaR1=QKtJh0MoP3Abmwg@mail.gmail.com' \
    --to=djc@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