| 1 |
>>>>> On Thu, 20 Feb 2014, Alexandre Rostovtsev wrote: |
| 2 |
|
| 3 |
> Unfortunately, at the same time, lots of other developers are going |
| 4 |
> to start adding support for building against gtk2 XOR gtk3. Because |
| 5 |
> of course "Gentoo is about choice", and the more choices, the |
| 6 |
> merrier, and the gtk3 flag has been declared as supported by the QA |
| 7 |
> team. And that means lots of REQUIRED_USE="^^ ( gtk gtk3 )". |
| 8 |
|
| 9 |
No, in most cases REQUIRED_USE would be against policy. The actual |
| 10 |
policy is to "pick one of the USE flags in conflict to favour and |
| 11 |
should alert the user that a particular flag is being used instead", |
| 12 |
see the devmanual: |
| 13 |
http://devmanual.gentoo.org/general-concepts/use-flags/index.html |
| 14 |
|
| 15 |
> For the gnome team this results in a headache: maintaining a big |
| 16 |
> list of "-gtk" / "-gtk3" entries in |
| 17 |
> targets/desktop/gnome/package.use so that gnome users get a sensible |
| 18 |
> choice and don't need to edit /etc/portage/* just to emerge widely |
| 19 |
> used desktop tools. |
| 20 |
|
| 21 |
Right, and that's exactly the reason why REQUIRED_USE should not be |
| 22 |
used, except where it's forced be reverse USE dependencies. Quoting |
| 23 |
the devmanual again: |
| 24 |
"Note: In order to avoid forcing users to micro-manage flags too much, |
| 25 |
REQUIRED_USE should be used sparingly. Follow the normal policy |
| 26 |
whenever it is possible to do a build that will presumably suit the |
| 27 |
user's needs." |
| 28 |
|
| 29 |
Ulrich |
Archives