From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-pms] [PATCH v2] ebuild-env-vars.tex: Allow SYSROOT & BROOT in pkg_setup
Date: Sun, 5 May 2019 20:43:18 +0200 [thread overview]
Message-ID: <20190505184318.1666-1-mgorny@gentoo.org> (raw)
Allow using SYSROOT & BROOT in pkg_setup(), when building from source.
This follows the earlier change allowing for build-time dependencies
in pkg_setup under the same circumstances.
---
ebuild-env-vars.tex | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index 56f959c..660d17b 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -132,19 +132,20 @@ variable.
table~\ref{tab:offset-env-vars-table} as supporting \t{EROOT}\@. The presence of a trailing
slash is EAPI dependent as listed in table~\ref{tab:trailing-slash}. \\
\t{SYSROOT} &
- \t{src_*} &
+ \t{src_*}, \t{pkg_setup}\footnote{Not necessarily present when installing from a binary
+ package.} &
No &
\featurelabel{sysroot} The absolute path to the root directory containing build dependencies
satisfied by \t{DEPEND}\@. Only for EAPIs listed in table~\ref{tab:added-env-vars-table}
as supporting \t{SYSROOT}. \\
\t{ESYSROOT} &
- \t{src_*} &
+ Ditto &
No &
Contains the concatenation of the paths in the \t{SYSROOT} and \t{EPREFIX} variables,
for convenience. See also the \t{EPREFIX} variable. Only for EAPIs listed
in table~\ref{tab:offset-env-vars-table} as supporting \t{ESYSROOT}. \\
\t{BROOT} &
- \t{src_*} &
+ Ditto &
No &
\featurelabel{broot} The absolute path to the root directory containing build dependencies
satisfied by \t{BDEPEND}, typically executable build tools. This includes any applicable offset
--
2.21.0
next reply other threads:[~2019-05-05 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 18:43 Michał Górny [this message]
2019-05-13 21:59 ` [gentoo-pms] [PATCH v2] ebuild-env-vars.tex: Allow SYSROOT & BROOT in pkg_setup Ulrich Mueller
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=20190505184318.1666-1-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-pms@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