Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Gentoo Portage Developer (http://www.linux-archive.org/gentoo-portage-developer/)
-   -   Document HDEPEND in ebuild(5) (http://www.linux-archive.org/gentoo-portage-developer/706777-document-hdepend-ebuild-5-a.html)

Dennis Schridde 09-23-2012 10:28 PM

Document HDEPEND in ebuild(5)
 
---
man/ebuild.5 | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)

diff --git a/man/ebuild.5 b/man/ebuild.5
index 5bb1afa..9fec816 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -316,6 +316,32 @@ the user does not specify any of the previous choices.
Note that if any of the packages listed are already merged, the package manager
will use that to consider the dependency satisfied.

+.SS "Cross-compilation"
+Portage supports cross-compilation into a subdirectory specified by fBROOTfR.
+.TP
+.B Host
+fIHostfR in this context means the platform hosting the build process, i.e.
+what autotools calls CBUILD. Its packages are contained in the root of the
+filesystem ("fI/fR"). If fBROOTfR is "fI/fR", all dependency types will
+be installed there. Otherwise (starting from fBEAPI 6fR) only fBHDEPENDfR
+is installed into "fI/fR". In fBEAPI 5fR and earlier, the behaviour is
+controlled by the fI--root-depsfR flag to fBemergefR(1), defaulting to
+install only fBDEPENDfR into the fIhostfR.
+.TP
+.B Target
+fITargetfR refers to the platform that the package will later run on, i.e.
+what autotools calls CHOST. The directory housing this system is specified by
+fBROOTfR. If it is different from "fI/fR", i.e. fIhostfR and
+fItargetfR are not the same, this variable contains the path to the directory
+housing the fItargetfR system. Starting from fBEAPI 6fR, fBDEPENDfR and
+fBRDEPENDfR list the fItargetfR dependencies, i.e. those to be installed
+into fBROOTfR. In fBEAPI 5fR and earlier, the fBemergefR(1) flag
+fI--root-depsfR controlled what the package manager installed there,
+defaulting to only fBRDEPENDfR.
+.PP
+See section fBVARIABLESfR for more information about the fBDEPENDfR,
+fBRDEPENDfR and fBHDEPENDfR variables.
+
.SH "VARIABLES"
.TP
.B Usage Notes
@@ -547,6 +573,11 @@ 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.

+Starting from fBEAPI 6fR, tools should go into the fBHDEPENDfR variable
+instead, as fBDEPENDfR will only be installed into the fItargetfR system
+and hence cannot be executed in a cross-compile setting. (See section
+fBCross-compilationfR for more information.)
+
You may use the syntax described above in the fBDependenciesfR section.
.TP
.B RDEPEND
@@ -559,6 +590,16 @@ implicitly set.

You may use the syntax described above in the fBDependenciesfR section.
.TP
+.B HDEPEND
+This should contain a list of all packages that are required to be executable
+during compilation of this program (aka fIhostfR buildtime dependencies).
+These are usually tools, like interpreters or (cross-)compilers.
+
+This variable is new in fBEAPI 6fR and will be installed into the fIhostfR
+system. (See section fBCross-compilationfR for more information.)
+
+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 (aka fIpostfR merge dependencies), but which may be installed by the
--
1.7.12

Zac Medico 09-24-2012 03:42 AM

Document HDEPEND in ebuild(5)
 
On 09/23/2012 03:28 PM, Dennis Schridde wrote:
> +This variable is new in fBEAPI 6fR and will be installed into the fIhostfR
> +system. (See section fBCross-compilationfR for more information.)

It's premature to say anything about EAPI 6. You should refer to
"experimental EAPI 5-hdepend" instead.
--
Thanks,
Zac

Dennis Schridde 09-24-2012 12:16 PM

Document HDEPEND in ebuild(5)
 
---
man/ebuild.5 | 46 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)

diff --git a/man/ebuild.5 b/man/ebuild.5
index 5bb1afa..a15bf55 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -316,6 +316,36 @@ the user does not specify any of the previous choices.
Note that if any of the packages listed are already merged, the package manager
will use that to consider the dependency satisfied.

+.SS "Cross-compilation"
+Portage supports cross-compilation into a subdirectory specified by fBROOTfR.
+.TP
+.B Host
+fIHostfR in this context means the platform hosting the build process, i.e.
+what autotools calls CBUILD.
+Its packages are contained in the root of the filesystem ("fI/fR").
+If fBROOTfR is "fI/fR", all dependency types will be installed there.
+Otherwise, starting from experimental fBEAPI 5-hdependfR, only fBHDEPENDfR
+is installed into "fI/fR".
+In fBEAPI 5fR and earlier, the behaviour is controlled by the
+fI--root-depsfR flag to fBemergefR(1), defaulting to install only
+fBDEPENDfR into the fIhostfR.
+.TP
+.B Target
+fITargetfR refers to the platform that the package will later run on, i.e.
+what autotools calls CHOST.
+The directory housing this system is specified by fBROOTfR.
+If it is different from "fI/fR", i.e. fIhostfR and fItargetfR are not the
+same, this variable contains the path to the directory housing the fItargetfR
+system.
+Starting from experimental fBEAPI 5-hdependfR, fBDEPENDfR and fBRDEPENDfR
+list the fItargetfR dependencies, i.e. those to be installed into fBROOTfR.
+In fBEAPI 5fR and earlier, the fBemergefR(1) flag fI--root-depsfR
+controlled what the package manager installed there, defaulting to only
+fBRDEPENDfR.
+.PP
+See section fBVARIABLESfR for more information about the fBDEPENDfR,
+fBRDEPENDfR and fBHDEPENDfR variables.
+
.SH "VARIABLES"
.TP
.B Usage Notes
@@ -547,6 +577,11 @@ 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.

+Starting from experimental fBEAPI 5-hdependfR, tools should go into the
+fBHDEPENDfR variable instead, as fBDEPENDfR will only be installed into the
+fItargetfR system and hence cannot be executed in a cross-compile setting.
+(See section fBCross-compilationfR for more information.)
+
You may use the syntax described above in the fBDependenciesfR section.
.TP
.B RDEPEND
@@ -559,6 +594,17 @@ implicitly set.

You may use the syntax described above in the fBDependenciesfR section.
.TP
+.B HDEPEND
+This should contain a list of all packages that are required to be executable
+during compilation of this program (aka fIhostfR buildtime dependencies).
+These are usually tools, like interpreters or (cross-)compilers.
+
+This variable is new in experimental fBEAPI 5-hdependfR and will be installed
+into the fIhostfR system.
+(See section fBCross-compilationfR for more information.)
+
+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 (aka fIpostfR merge dependencies), but which may be installed by the
--
1.7.12


All times are GMT. The time now is 12:57 AM.

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