Gentoo Archives: gentoo-portage-dev

From: Dennis Schridde <devurandom@×××.net>
To: gentoo-portage-dev@l.g.o
Cc: Dennis Schridde <devurandom@×××.net>
Subject: [gentoo-portage-dev] [PATCH 1/2] Document HDEPEND in ebuild(5)
Date: Mon, 24 Sep 2012 15:04:48
Message-Id: 1348488962-4275-2-git-send-email-devurandom@gmx.net
In Reply to: [gentoo-portage-dev] Please review: manpage-hdepend by Dennis Schridde
1 ---
2 man/ebuild.5 | 46 ++++++++++++++++++++++++++++++++++++++++++++++
3 1 file changed, 46 insertions(+)
4
5 diff --git a/man/ebuild.5 b/man/ebuild.5
6 index 5bb1afa..a15bf55 100644
7 --- a/man/ebuild.5
8 +++ b/man/ebuild.5
9 @@ -316,6 +316,36 @@ the user does not specify any of the previous choices.
10 Note that if any of the packages listed are already merged, the package manager
11 will use that to consider the dependency satisfied.
12
13 +.SS "Cross-compilation"
14 +Portage supports cross-compilation into a subdirectory specified by \fBROOT\fR.
15 +.TP
16 +.B Host
17 +\fIHost\fR in this context means the platform hosting the build process, i.e.
18 +what autotools calls CBUILD.
19 +Its packages are contained in the root of the filesystem ("\fI/\fR").
20 +If \fBROOT\fR is "\fI/\fR", all dependency types will be installed there.
21 +Otherwise, starting from experimental \fBEAPI 5-hdepend\fR, only \fBHDEPEND\fR
22 +is installed into "\fI/\fR".
23 +In \fBEAPI 5\fR and earlier, the behaviour is controlled by the
24 +\fI\-\-root-deps\fR flag to \fBemerge\fR(1), defaulting to install only
25 +\fBDEPEND\fR into the \fIhost\fR.
26 +.TP
27 +.B Target
28 +\fITarget\fR refers to the platform that the package will later run on, i.e.
29 +what autotools calls CHOST.
30 +The directory housing this system is specified by \fBROOT\fR.
31 +If it is different from "\fI/\fR", i.e. \fIhost\fR and \fItarget\fR are not the
32 +same, this variable contains the path to the directory housing the \fItarget\fR
33 +system.
34 +Starting from experimental \fBEAPI 5-hdepend\fR, \fBDEPEND\fR and \fBRDEPEND\fR
35 +list the \fItarget\fR dependencies, i.e. those to be installed into \fBROOT\fR.
36 +In \fBEAPI 5\fR and earlier, the \fBemerge\fR(1) flag \fI\-\-root-deps\fR
37 +controlled what the package manager installed there, defaulting to only
38 +\fBRDEPEND\fR.
39 +.PP
40 +See section \fBVARIABLES\fR for more information about the \fBDEPEND\fR,
41 +\fBRDEPEND\fR and \fBHDEPEND\fR variables.
42 +
43 .SH "VARIABLES"
44 .TP
45 .B Usage Notes
46 @@ -547,6 +577,11 @@ This should contain a list of all packages that are required for the program
47 to compile (aka \fIbuildtime\fR dependencies). These are usually libraries and
48 headers.
49
50 +Starting from experimental \fBEAPI 5-hdepend\fR, tools should go into the
51 +\fBHDEPEND\fR variable instead, as \fBDEPEND\fR will only be installed into the
52 +\fItarget\fR system and hence cannot be executed in a cross\-compile setting.
53 +(See section \fBCross\-compilation\fR for more information.)
54 +
55 You may use the syntax described above in the \fBDependencies\fR section.
56 .TP
57 .B RDEPEND
58 @@ -559,6 +594,17 @@ implicitly set.
59
60 You may use the syntax described above in the \fBDependencies\fR section.
61 .TP
62 +.B HDEPEND
63 +This should contain a list of all packages that are required to be executable
64 +during compilation of this program (aka \fIhost\fR buildtime dependencies).
65 +These are usually tools, like interpreters or (cross\-)compilers.
66 +
67 +This variable is new in experimental \fBEAPI 5-hdepend\fR and will be installed
68 +into the \fIhost\fR system.
69 +(See section \fBCross-compilation\fR for more information.)
70 +
71 +You may use the syntax described above in the \fBDependencies\fR section.
72 +.TP
73 .B PDEPEND
74 This should contain a list of all packages that should be merged after this
75 one (aka \fIpost\fR merge dependencies), but which may be installed by the
76 --
77 1.7.12