From: Dennis Schridde Date: Sun, 23 Sep 2012 18:01:12 +0000 (+0200) Subject: Improve wording of *DEPEND variable description in ebuild(5) a bit X-Git-Tag: v2.2.0_alpha132~3 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=9dd83334c56262de44b0efa3c98777f1a3cc27af;p=portage.git Improve wording of *DEPEND variable description in ebuild(5) a bit --- diff --git a/man/ebuild.5 b/man/ebuild.5 index 0d4d4e538..d340c8587 100644 --- a/man/ebuild.5 +++ b/man/ebuild.5 @@ -543,27 +543,32 @@ repo\-level USE settings, since profile and user configuration settings override them. .TP .B DEPEND -This should contain a list of all packages that are required for the -program to compile as described in \fBDependencies\fR. +This should contain a list of all packages that are required for the program +to compile (aka \fIbuildtime\fR dependencies). These are usually libraries and +headers. + +You may use the syntax described above in the \fBDependencies\fR section. .TP .B RDEPEND This should contain a list of all packages that are required for this -program to run (aka runtime depend). If this is not set in \fBEAPI 3\fR -or earlier, then it defaults to the value of \fBDEPEND\fR. In -\fBEAPI 4\fR or later, \fBRDEPEND\fR will never be implicitly set. +program to run (aka \fIruntime\fR dependencies). These are usually libraries. + +In \fBEAPI 3\fR or earlier, if this is not set, then it defaults to the value +of \fBDEPEND\fR. In \fBEAPI 4\fR or later, \fBRDEPEND\fR will never be +implicitly set. -You may use the same syntax to vary dependencies as seen above in \fBDependencies\fR. +You may use the syntax described above in the \fBDependencies\fR section. .TP .B PDEPEND This should contain a list of all packages that should be merged after this -one, but which may be installed by the package manager at any time, if that is -not possible. +one (aka \fIpost\fR merge dependencies), but which may be installed by the +package manager at any time, if that is not possible. .B ***WARNING*** .br Use this only as last resort to break cyclic dependencies! -You may use the same syntax to vary dependencies as seen above in \fBDependencies\fR. +You may use the syntax described above in the \fBDependencies\fR section. .TP .B REQUIRED_USE Beginning with \fBEAPI 4\fR, the \fBREQUIRED_USE\fR variable can be