From: Dennis Schridde <devurandom@gmx.net>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Dennis Schridde <devurandom@gmx.net>
Subject: [gentoo-portage-dev] [PATCH 4/5] Improve wording of *DEPEND variable description in ebuild(5) a bit
Date: Mon, 24 Sep 2012 00:25:39 +0200 [thread overview]
Message-ID: <1348439140-28207-5-git-send-email-devurandom@gmx.net> (raw)
In-Reply-To: <1348439140-28207-1-git-send-email-devurandom@gmx.net>
---
man/ebuild.5 | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/man/ebuild.5 b/man/ebuild.5
index 3f28fce..5bb1afa 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
--
1.7.12
next prev parent reply other threads:[~2012-09-24 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 22:25 [gentoo-portage-dev] Please review: manpage-cleanup Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 1/5] Adjust code of first paragraph of ebuild(5) to 80 char width Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 2/5] Fix referencens to Dependencies section of ebuild(5) Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 3/5] Better documentation of PDEPEND in ebuild(5) Dennis Schridde
2012-09-23 22:25 ` Dennis Schridde [this message]
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 5/5] Reorder description of --root-deps in emerge(1) Dennis Schridde
2012-09-23 22:38 ` [gentoo-portage-dev] Please review: manpage-cleanup Dennis Schridde
2012-09-24 2:46 ` Zac Medico
2012-09-24 9:54 ` Dennis Schridde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1348439140-28207-5-git-send-email-devurandom@gmx.net \
--to=devurandom@gmx.net \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox