Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Gentoo Portage Developer (http://www.linux-archive.org/gentoo-portage-developer/)
-   -   Improve wording of *DEPEND variable description in ebuild(5) a bit (http://www.linux-archive.org/gentoo-portage-developer/706775-improve-wording-depend-variable-description-ebuild-5-bit.html)

Dennis Schridde 09-23-2012 10:25 PM

Improve wording of *DEPEND variable description in ebuild(5) a bit
 
---
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 fBDependenciesfR.
+This should contain a list of all packages that are required for the program
+to compile (aka fIbuildtimefR dependencies). These are usually libraries and
+headers.
+
+You may use the syntax described above in the fBDependenciesfR 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 3fR
-or earlier, then it defaults to the value of fBDEPENDfR. In
-fBEAPI 4fR or later, fBRDEPENDfR will never be implicitly set.
+program to run (aka fIruntimefR dependencies). These are usually libraries.
+
+In fBEAPI 3fR or earlier, if this is not set, then it defaults to the value
+of fBDEPENDfR. In fBEAPI 4fR or later, fBRDEPENDfR will never be
+implicitly set.

-You may use the same syntax to vary dependencies as seen above in fBDependenciesfR.
+You may use the syntax described above in the fBDependenciesfR 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 fIpostfR 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 fBDependenciesfR.
+You may use the syntax described above in the fBDependenciesfR section.
.TP
.B REQUIRED_USE
Beginning with fBEAPI 4fR, the fBREQUIRED_USEfR variable can be
--
1.7.12

Dennis Schridde 09-23-2012 10:32 PM

Improve wording of *DEPEND variable description in ebuild(5) a bit
 
---
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 fBDependenciesfR.
+This should contain a list of all packages that are required for the program
+to compile (aka fIbuildtimefR dependencies). These are usually libraries and
+headers.
+
+You may use the syntax described above in the fBDependenciesfR 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 3fR
-or earlier, then it defaults to the value of fBDEPENDfR. In
-fBEAPI 4fR or later, fBRDEPENDfR will never be implicitly set.
+program to run (aka fIruntimefR dependencies). These are usually libraries.
+
+In fBEAPI 3fR or earlier, if this is not set, then it defaults to the value
+of fBDEPENDfR. In fBEAPI 4fR or later, fBRDEPENDfR will never be
+implicitly set.

-You may use the same syntax to vary dependencies as seen above in fBDependenciesfR.
+You may use the syntax described above in the fBDependenciesfR 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 fIpostfR 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 fBDependenciesfR.
+You may use the syntax described above in the fBDependenciesfR section.
.TP
.B REQUIRED_USE
Beginning with fBEAPI 4fR, the fBREQUIRED_USEfR variable can be
--
1.7.12


All times are GMT. The time now is 10:48 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.