From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM
Date: Thu, 4 Feb 2016 13:22:24 +0100 [thread overview]
Message-ID: <20160204132224.581321ad@gentoo.org> (raw)
In-Reply-To: <CAKmKYaBvnc_PZ9i5CM5HRQ5=fOb3KsFaR1=QKtJh0MoP3Abmwg@mail.gmail.com>
On Thu, 4 Feb 2016 13:01:25 +0100
Dirkjan Ochtman <djc@gentoo.org> wrote:
[...]
> 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.
They're just useflags, equery properly displays their description, and
you can set them in pacakge.use equally well, so you don't have to
learn anything new. You get a new way to set them via variables in
make.conf, which I agree is debatable, but doesn't add complexity.
[...]
> 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.
Well, categorizing useflags, esp. for packages with a lot of them,
certainly helps me when I need to review what to enable and what not.
Alexis.
next prev parent reply other threads:[~2016-02-04 12:22 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 [this message]
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=20160204132224.581321ad@gentoo.org \
--to=aballier@gentoo.org \
--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