configure arguments.
</para>
</section>
+<section id='package-ebuild-eapi-4-helpers-use-with-enable-empty-third-arg'>
+<title>use_with and use_enable support empty third argument</title>
+<para>
+Beginning with EAPI 4, an empty third argument
+is recognized. In EAPI 3 and earlier, an empty third
+argument is treated as if it weren't provided.
+</para>
+</section>
</section>
<section id='package-ebuild-eapi-4-metadata'>
<title>Metadata</title>
name]\fR will be echoed. If \fIUSE item\fR is not in the \fBUSE\fR variable,
then the string \fI\-\-without\-[configure name]\fR will be echoed. If
\fIconfigure name\fR is not specified, then \fIUSE item\fR will be used in
-its place.
+its place. Beginning with \fBEAPI 4\fR, an empty \fIconfigure opt\fR argument
+is recognized. In \fBEAPI 3\fR and earlier, an empty \fIconfigure opt\fR
+argument is treated as if it weren't provided.
.RS
.TP
.I Examples:
\fBuse_enable\fR \fI<USE item>\fR \fI[configure name]\fR \fI[configure opt]\fR
Same as \fBuse_with\fR above, except that the configure options are
\fI\-\-enable\-\fR instead of \fI\-\-with\-\fR and \fI\-\-disable\-\fR instead of
-\fI\-\-without\-\fR.
+\fI\-\-without\-\fR. Beginning with \fBEAPI 4\fR, an empty \fIconfigure opt\fR
+argument is recognized. In \fBEAPI 3\fR and earlier, an empty
+\fIconfigure opt\fR argument is treated as if it weren't provided.
.TP
\fBhas\fR \fI<item>\fR \fI<item list>\fR
If \fIitem\fR is in \fIitem list\fR, then \fIitem\fR is echoed and \fBhas\fR