From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [gentoo-user] Why IDEPEND's context is BHOST?
Date: Thu, 1 Sep 2022 11:09:29 -0400 [thread overview]
Message-ID: <YxDLKcDawictzHXf@eversor> (raw)
In-Reply-To: <1662042406.373307990@f110.i.mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Thu, Sep 01, 2022 at 05:26:46PM +0300, Alexander Kurakin wrote:
>
> Good day!
>
> [1] says:
>
> > idepend Additionally, in EAPIs listed in table 8.4 as supporting IDEPEND, install-time dependencies can be specified. These dependencies are binary compatible with the native build system (CBUILD).
>
> But we install and use (run at install-time) dependencies on host system (CHOST), don’t we? Why CBUILD is mentioned above, instead?
If cross-building to a different ROOT, e.g. amd64 CBUILD to a aarch64
CHOST, then amd64 will need deps to run pkg_postinst from its arch
(which IDEPEND will provide).
Of course, aarch64 will /also/ need these deps so it can emerge or
unmerge a binpkg, also provided by IDEPEND.
Before EAPI8 the best you could do to represent this was to have
the dependency in both RDEPEND and BDEPEND, but this lack a use-case
where you cross-emerge a binpkg given it won't pull BDEPEND (not
building) and then RDEPEND is for the wrong arch.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-01 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 14:26 [gentoo-user] [gentoo-user] Why IDEPEND's context is BHOST? Alexander Kurakin
2022-09-01 15:09 ` Ionen Wolkens [this message]
2022-09-02 8:03 ` [gentoo-user] [gentoo-ser] " Alexander Kurakin
2022-09-02 19:19 ` Ionen Wolkens
2022-09-03 15:14 ` [gentoo-user] " Alexander Kurakin
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=YxDLKcDawictzHXf@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-user@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