On 02/09/2011 03:11 PM, Zac Medico wrote: > In order to try to avoid forcing users to micro-manage flags too much, > it might make sense to avoid REQUIRED_USE whenever it's possible to do a > build that will almost certainly suit the user's needs. The most common > case that I can imagine where REQUIRED_USE is really necessary is for > libraries were reverse USE dependencies might be broken without it.
To clarify about issues with reverse USE dependencies, I mean any library with something like REQUIRED_USE="^^ ( a b )" where either a or b would be specified in reverse USE dependencies. Also, it's worth noting that something like REQUIRED_USE="c? ( ^^ ( a b ) )" may not need REQUIRED_USE if reverse USE dependencies dep on c rather than a or b. -- Thanks, Zac
