From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFD: new global USE flag gtk3
Date: Thu, 20 Feb 2014 10:26:35 +0100 [thread overview]
Message-ID: <21253.51787.375622.975653@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1392886757.7587.38.camel@rook>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
>>>>> On Thu, 20 Feb 2014, Alexandre Rostovtsev wrote:
> Unfortunately, at the same time, lots of other developers are going
> to start adding support for building against gtk2 XOR gtk3. Because
> of course "Gentoo is about choice", and the more choices, the
> merrier, and the gtk3 flag has been declared as supported by the QA
> team. And that means lots of REQUIRED_USE="^^ ( gtk gtk3 )".
No, in most cases REQUIRED_USE would be against policy. The actual
policy is to "pick one of the USE flags in conflict to favour and
should alert the user that a particular flag is being used instead",
see the devmanual:
http://devmanual.gentoo.org/general-concepts/use-flags/index.html
> For the gnome team this results in a headache: maintaining a big
> list of "-gtk" / "-gtk3" entries in
> targets/desktop/gnome/package.use so that gnome users get a sensible
> choice and don't need to edit /etc/portage/* just to emerge widely
> used desktop tools.
Right, and that's exactly the reason why REQUIRED_USE should not be
used, except where it's forced be reverse USE dependencies. Quoting
the devmanual again:
"Note: In order to avoid forcing users to micro-manage flags too much,
REQUIRED_USE should be used sparingly. Follow the normal policy
whenever it is possible to do a build that will presumably suit the
user's needs."
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-02-20 9:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 22:23 [gentoo-dev] RFD: new global USE flag gtk3 Ulrich Mueller
2014-02-20 5:55 ` Samuli Suominen
2014-02-20 7:44 ` Steev Klimaszewski
2014-02-20 8:11 ` Michał Górny
2014-02-20 8:49 ` Ulrich Mueller
2014-02-20 8:55 ` Steev Klimaszewski
2014-02-20 10:05 ` Alex Alexander
2014-02-20 8:40 ` Samuli Suominen
2014-02-20 8:47 ` Steev Klimaszewski
2014-02-20 8:59 ` Alexandre Rostovtsev
2014-02-20 9:23 ` Steev Klimaszewski
2014-02-20 9:28 ` Samuli Suominen
2014-02-20 10:38 ` Lars Wendler
2014-02-20 9:52 ` Alexandre Rostovtsev
2014-02-20 9:26 ` Ulrich Mueller [this message]
2014-02-20 10:16 ` Alexandre Rostovtsev
2014-02-20 10:48 ` Ulrich Mueller
2014-02-20 15:32 ` Ciaran McCreesh
2014-02-20 16:41 ` hasufell
2014-02-20 16:46 ` Ciaran McCreesh
2014-02-22 20:57 ` [gentoo-dev] " Ryan Hill
2014-02-22 21:09 ` Alexandre Rostovtsev
2014-02-22 21:50 ` Ryan Hill
2014-02-22 21:59 ` Ryan Hill
2014-02-22 22:11 ` Alexandre Rostovtsev
2014-02-20 9:26 ` [gentoo-dev] " Samuli Suominen
2014-02-20 16:27 ` Tom Wijsman
2014-02-25 15:28 ` Samuli Suominen
2014-02-25 19:22 ` Tom Wijsman
2014-03-15 18:55 ` Raymond Jennings
2014-03-16 14:27 ` Tom Wijsman
2014-02-22 19:27 ` [gentoo-dev] " Ryan Hill
2014-02-20 10:07 ` Duncan
2014-02-20 10:27 ` Samuli Suominen
2014-02-20 12:21 ` Andreas K. Huettel
2014-02-20 13:03 ` Matt Turner
2014-02-20 14:08 ` Alex Alexander
2014-02-20 16:51 ` Tom Wijsman
2014-02-23 16:59 ` Peter Stuge
2014-02-24 0:49 ` Tom Wijsman
2014-02-24 0:59 ` Peter Stuge
2014-02-24 1:06 ` Tom Wijsman
2014-02-24 2:16 ` Peter Stuge
2014-02-24 3:01 ` Tom Wijsman
2014-02-25 12:06 ` Alex Alexander
2014-02-20 8:24 ` [gentoo-dev] " Lars Wendler
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=21253.51787.375622.975653@a1i15.kph.uni-mainz.de \
--to=ulm@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