| 1 |
On 02/08/2011 06:20 PM, Ryan Hill wrote: |
| 2 |
> The guideline I usually follow is that flags depending on another flag being |
| 3 |
> set (eg. png needs X) should be ignored (you can always ewarn). For flags |
| 4 |
> that conflict with other flags (exactly one of many, if-this-not-this) use |
| 5 |
> REQUIRED_USE. Does that make sense? |
| 6 |
|
| 7 |
In order to try to avoid forcing users to micro-manage flags too much, |
| 8 |
it might make sense to avoid REQUIRED_USE whenever it's possible to do a |
| 9 |
build that will almost certainly suit the user's needs. The most common |
| 10 |
case that I can imagine where REQUIRED_USE is really necessary is for |
| 11 |
libraries were reverse USE dependencies might be broken without it. |
| 12 |
-- |
| 13 |
Thanks, |
| 14 |
Zac |
Archives