From: Dennis Schridde Date: Tue, 25 Sep 2012 13:58:22 +0000 (+0200) Subject: Put lengthy install-location documentation into an own paragraph for cross-compile... X-Git-Tag: v2.2.0_alpha133~15 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=0c09bd722b091b6efd8c2c0b3a039965dd6fca58;p=portage.git Put lengthy install-location documentation into an own paragraph for cross-compile docs in ebuild(5) --- diff --git a/man/ebuild.5 b/man/ebuild.5 index fc06eee65..3c2200c6f 100644 --- a/man/ebuild.5 +++ b/man/ebuild.5 @@ -323,6 +323,7 @@ Portage supports cross-compilation into a subdirectory specified by \fBROOT\fR. \fIHost\fR 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 \fBROOT\fR is "\fI/\fR", all dependency types will be installed there. Otherwise, for EAPIs that support \fBHDEPEND\fR (experimental \fBEAPI 5-hdepend\fR), only \fBHDEPEND\fR is installed into "\fI/\fR". @@ -337,6 +338,7 @@ The directory housing this system is specified by \fBROOT\fR. If it is different from "\fI/\fR", i.e. \fIhost\fR and \fItarget\fR are not the same, this variable contains the path to the directory housing the \fItarget\fR system. + For EAPIs that support \fBHDEPEND\fR (experimental \fBEAPI 5-hdepend\fR), \fBDEPEND\fR, \fBRDEPEND\fR, and \fBPDEPEND\fR list the \fItarget\fR dependencies, i.e. those to be installed into \fBROOT\fR.