ebuild(5): REQUIRED_USE in EAPI 4

diff --git a/man/ebuild.5 b/man/ebuild.5
index 22cec1761d5d39aaa43f466e4384b8576334a383..9ceee590d538d54105780181b702f5665996c2d6 100644 (file)
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -444,6 +444,24 @@ but may be merged before if need be.
 .br
 You may use the same syntax to vary dependencies as seen above in \fBDEPEND\fR.
 .TP
+\fBREQUIRED_USE\fR
+Beginning with \fBEAPI 4\fR, the \fBREQUIRED_USE\fR variable can be
+used to specify combinations of \fBUSE\fR flags that are allowed
+or not allowed. Elements can be nested when necessary.
+.TS
+l l
+__
+l l.
+Behavior       Expression
+
+If flag1 enabled then flag2 disabled   flag1? ( !flag2 )
+If flag1 enabled then flag2 disabled   flag1? ( flag2 )
+If flag1 disabled then flag2 enabled   !flag1? ( flag2 )
+If flag1 disabled then flag2 disabled  !flag1? ( !flag2 )
+Must enable any one or more (inclusive or)     || ( flag1 flag2 flag3 )
+Must enable exactly one but not more (exclusive or)    ^^ ( flag1 flag2 flag3 )
+.TE
+.TP
 \fBRESTRICT\fR = \fI[strip,mirror,fetch,userpriv]\fR
 This should be a space delimited list of portage features to restrict.
 You may use conditional syntax to vary restrictions as seen above in DEPEND.