>>>>> On Mon, 07 May 2012, Zac Medico wrote: > Another possible way to model this kind of relationship would be to > us REQUIRED_USE to enforce relationships with the qt and gtk flags:
> REQUIRED_USE="webkit? ( qt ) !webkit? ( !qt ) qt? ( webkit ) !qt? ( > !webkit )" This line just says that either both webkit and qt must be set, or neither of them. In other words, that the ebuild has redundant flags, which IMHO should be avoided. > versus > REQUIRED_USE="webkit? ( gtk ) !webkit? ( !gtk ) gtk? ( webkit ) !gtk? ( > !webkit )" > It's pretty awkward with the existing operators, but we could extend > the REQUIRED_USE syntax to support an equivalent operator in a > future EAPI. As far as I can see, it is equivalent to: REQUIRED_USE="^^ ( webkit !qt )" (or analog for the gtk case). But see above. Ulrich
