On 02/08/2011 06:20 PM, Ryan Hill wrote: > The guideline I usually follow is that flags depending on another flag being > set (eg. png needs X) should be ignored (you can always ewarn). For flags > that conflict with other flags (exactly one of many, if-this-not-this) use > REQUIRED_USE. Does that make sense?
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. -- Thanks, Zac
