Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] add global useflag: webkit
Date: Tue, 08 May 2012 04:36:21
Message-Id: 4FA8A285.8080300@gentoo.org
In Reply to: Re: [gentoo-dev] add global useflag: webkit by "Michał Górny"
1 On 05/07/2012 09:07 PM, Michał Górny wrote:
2 > On Mon, 07 May 2012 20:58:18 -0700
3 > Zac Medico <zmedico@g.o> wrote:
4 >
5 >> -----BEGIN PGP SIGNED MESSAGE-----
6 >> Hash: SHA1
7 >>
8 >> On 05/07/2012 08:50 PM, Michał Górny wrote:
9 >>> On Mon, 07 May 2012 14:41:33 -0700 Zac Medico <zmedico@g.o>
10 >>> wrote:
11 >>>
12 >>>> On 05/07/2012 01:43 PM, Michał Górny wrote:
13 >>>>> On Mon, 07 May 2012 13:24:31 -0700 Zac Medico
14 >>>>> <zmedico@g.o> wrote:
15 >>>>>
16 >>>>>> On 05/07/2012 12:18 PM, Ulrich Mueller wrote:
17 >>>>>>>>>>>> On Mon, 7 May 2012, Ciaran McCreesh wrote:
18 >>>>>>>
19 >>>>>>>> I propose:
20 >>>>>>>
21 >>>>>>>> REQUIRED_USE="== ( qt webkit )"
22 >>>>>>>
23 >>>>>>> But this just means that the ebuild has redundant USE
24 >>>>>>> flags, so one of them shouldn't be in IUSE, in the first
25 >>>>>>> place.
26 >>>>>>
27 >>>>>> It serves to convey meaning, such that a user who has
28 >>>>>> disabled the qt USE flag will get a meaningful prompt if that
29 >>>>>> flag is required for webkit support. This kind of information
30 >>>>>> could be useful to some people, and it may be preferable to
31 >>>>>> having a separate webkit-qt flag.
32 >>>>>
33 >>>>> If 'qt' flag is required for webkit support, it's 'webkit? ( qt
34 >>>>> )'.
35 >>>>
36 >>>> What if '!webkit? ( !qt )' also applies though? As an alternative
37 >>>> to listing both constraints separately, you could combine them as
38 >>>> '^^ ( webkit !qt )', or add support for '== ( qt webkit )' to
39 >>>> make the expression easier to read.
40 >>>
41 >>> Then it's pointless to have the 'webkit' flag which doesn't
42 >>> control anything.
43 >>
44 >> Generalize the discussion to be about two abstract flags "x" and "y"
45 >> that have the same kind of relationship, where each one actually does
46 >> control something, but the two features are intertwined in a
47 >> particular package such that they must both be enabled or disabled in
48 >> unison.
49 >
50 > Then please show me an example of that.
51
52 I don't see any offhand. I guess it's fairly uncommon, or non-existent.
53 --
54 Thanks,
55 Zac