| 1 |
On 05/07/2012 11:24 PM, Zac Medico wrote: |
| 2 |
> On 05/07/2012 12:18 PM, Ulrich Mueller wrote: |
| 3 |
>>>>>>> On Mon, 7 May 2012, Ciaran McCreesh wrote: |
| 4 |
>> |
| 5 |
>>> I propose: |
| 6 |
>> |
| 7 |
>>> REQUIRED_USE="== ( qt webkit )" |
| 8 |
>> |
| 9 |
>> But this just means that the ebuild has redundant USE flags, so one of |
| 10 |
>> them shouldn't be in IUSE, in the first place. |
| 11 |
> |
| 12 |
> It serves to convey meaning, such that a user who has disabled the qt |
| 13 |
> USE flag will get a meaningful prompt if that flag is required for |
| 14 |
> webkit support. This kind of information could be useful to some people, |
| 15 |
> and it may be preferable to having a separate webkit-qt flag. |
| 16 |
|
| 17 |
ulm is right, it would still show up as an redudant USE flag as, |
| 18 |
the preferable result is that even KDE/Qt4 users get webkit-gtk |
| 19 |
installed if it's the rendering engine provided by the package. |
| 20 |
GTK+ is just graphical toolkit and not directly GNOME (like KDE users |
| 21 |
avoiding GNOME). By this same logic both USE="gtk qt4" are enabled in |
| 22 |
the desktop profile. |
| 23 |
I don't think we have any packages with *both* webkit-gtk and webkit-qt |
| 24 |
supports in tree (do we?). |
Archives