From: hasufell <hasufell@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE="gui"
Date: Sat, 12 Sep 2015 13:47:09 +0200 [thread overview]
Message-ID: <55F410BD.1040805@gentoo.org> (raw)
In-Reply-To: <55F36950.7050803@gentoo.org>
On 09/12/2015 01:52 AM, Daniel Campbell wrote:
> On 09/11/2015 01:34 PM, hasufell wrote:
>> I already use IUSE=gui and will keep doing that.
>
>> USE flags in gentoo are the best and the worst thing at the same
>> time. They are also mostly the main reason people don't like
>> gentoo, because USE flags are (for todays situation) pretty much
>> not an appropriate pattern to reflect real-world configuration. To
>> be more precise... USE flags are first-class citizens and there is
>> only one layer of them. There's not configuration
>> pattern/abstraction behind them. If you wonder what I am talking
>> about, have a look at NixOS. The reason we lack proper declarative
>> configuration is also the reason we had to introduce this ugliness
>> called REQUIRED_USE. Instead of saying "gui.gtk" we say
>> "REQUIRED_USE="gui? ( || ( gtk ... ) )". And it will get worse. I
>> wonder when people start realizing that.
>
>
> So are you suggesting maybe we come up with namespaced USE flags? That
> would be interesting.
>
I'm not sure we can do that without breaking gentoo. At least, it would
be a _huge_ EAPI change.
It would require a lot of PM work, would break our configuration format
(if you want to do it properly) and probably have other side effects for
running systems.
And if you have followed NixOS development... you know that you can
screw this up as well, because consistency is even more important if you
really want declarative configuration. And I'm not sure there is enough
interest in consistency in gentoo. People seem to be fine with micro
managing USE flags in order to achieve a particular configuration state
which can break arbitrarily on any update.
next prev parent reply other threads:[~2015-09-12 11:47 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 7:20 [gentoo-dev] www-client/chromium gtk3 support Paweł Hajdan, Jr.
2015-09-09 7:24 ` Daniel Campbell
2015-09-09 8:52 ` Andrew Savchenko
2015-09-09 10:37 ` hasufell
2015-09-09 13:17 ` Brian Dolbec
2015-09-09 13:31 ` hasufell
2015-09-10 6:21 ` Daniel Campbell
2015-09-10 8:47 ` hasufell
2015-09-10 10:45 ` Rich Freeman
2015-09-10 10:50 ` hasufell
2015-09-10 12:03 ` Rich Freeman
2015-09-10 12:13 ` hasufell
2015-09-10 12:25 ` Rich Freeman
2015-09-10 12:33 ` hasufell
2015-09-10 12:44 ` Rich Freeman
2015-09-10 12:53 ` hasufell
2015-09-10 13:10 ` Rich Freeman
2015-09-10 15:35 ` hasufell
2015-09-10 15:41 ` Alec Warner
2015-09-10 15:50 ` Rich Freeman
2015-09-10 16:50 ` hasufell
2015-09-10 16:51 ` [gentoo-dev] " Duncan
2015-09-10 13:38 ` [gentoo-dev] " Alan McKinnon
2015-09-10 12:46 ` Alec Ten Harmsel
2015-09-10 13:07 ` Michał Górny
2015-09-10 13:20 ` Rich Freeman
2015-09-10 14:31 ` Vadim A. Misbakh-Soloviov
2015-09-10 15:38 ` Alec Warner
2015-09-10 16:37 ` Vadim A. Misbakh-Soloviov
2015-09-10 16:57 ` hasufell
2015-09-10 17:17 ` Rich Freeman
2015-09-10 18:05 ` hasufell
2015-09-10 18:22 ` Rich Freeman
2015-09-10 18:30 ` Paweł Hajdan, Jr.
2015-09-10 17:43 ` [gentoo-dev] " Duncan
2015-09-10 19:04 ` Vadim A. Misbakh-Soloviov
2015-09-10 18:50 ` [gentoo-dev] " Vadim A. Misbakh-Soloviov
2015-09-10 16:24 ` Alec Ten Harmsel
2015-09-10 16:50 ` Vadim A. Misbakh-Soloviov
2015-09-10 12:47 ` Michael Orlitzky
2015-09-10 16:21 ` [gentoo-dev] " Duncan
2015-09-10 18:15 ` [gentoo-dev] " Daniel Campbell
2015-09-10 18:21 ` hasufell
2015-09-10 18:26 ` Rich Freeman
2015-09-11 9:03 ` Daniel Campbell
2015-09-11 12:13 ` Rich Freeman
2015-09-11 17:11 ` [gentoo-dev] " Duncan
2015-09-11 17:41 ` Rich Freeman
2015-09-11 18:03 ` [gentoo-dev] USE="gui" Ian Stakenvicius
2015-09-11 18:16 ` Rich Freeman
2015-09-11 20:34 ` hasufell
2015-09-11 23:52 ` Daniel Campbell
2015-09-12 11:47 ` hasufell [this message]
2015-09-12 2:29 ` [gentoo-dev] USE="gui" Duncan
2015-09-12 4:45 ` Dale
2015-09-12 2:24 ` Duncan
2015-09-12 4:55 ` [gentoo-dev] www-client/chromium gtk3 support Raymond Jennings
2015-09-12 10:00 ` [gentoo-dev] " Duncan
2015-09-12 10:48 ` Rich Freeman
2015-09-13 5:07 ` Duncan
2015-09-12 10:04 ` [gentoo-dev] " Rich Freeman
2015-09-09 10:06 ` [gentoo-dev] Re: firefox gtk3 status, danger of gtk2 in-tree deprecation? (was: www-client/chromium gtk3 support) Duncan
2015-09-09 15:12 ` »Q«
2015-09-10 2:23 ` Duncan
2015-09-09 15:32 ` [gentoo-dev] Re: firefox gtk3 status, danger of gtk2 in-tree deprecation? Ian Stakenvicius
2015-09-10 2:02 ` Duncan
2015-09-09 13:47 ` [gentoo-dev] www-client/chromium gtk3 support Alexandre Rostovtsev
2015-09-10 6:28 ` Daniel Campbell
2015-09-09 15:00 ` Mike Gilbert
2015-09-09 15:10 ` Alexandre Rostovtsev
2015-09-09 15:16 ` Alec Warner
2015-09-09 15:40 ` Ian Stakenvicius
2015-09-09 15:48 ` hasufell
2015-09-09 16:14 ` Ian Stakenvicius
2015-09-09 16:36 ` hasufell
2015-09-09 18:17 ` Paweł Hajdan, Jr.
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 6:58 [gentoo-dev] About how to handle wxGTK based packages with gnome profiles Pacho Ramos
2012-04-10 7:12 ` "Paweł Hajdan, Jr."
2012-04-16 8:11 ` [gentoo-dev] USE=gui? (was: About how to handle wxGTK based packages with gnome profiles) Michał Górny
2012-04-16 8:22 ` [gentoo-dev] USE=gui? Samuli Suominen
2012-04-16 14:49 ` Alexis Ballier
2012-04-16 17:12 ` Michał Górny
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=55F410BD.1040805@gentoo.org \
--to=hasufell@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