[gentoo-user] [gentoo-user] Why IDEPEND's context is BHOST?

[gentoo-user] [gentoo-user] Why IDEPEND's context is BHOST?

[Alexander Kurakin]

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]


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?
 
Thanks.
 
Sincerely,
Alexander Kurakin.
 
---
 
[1]: https://projects.gentoo.org/pms/8/pms.html#x1-720008.1

[-- Attachment #2: Type: text/html, Size: 1289 bytes --]

Re: [gentoo-user] [gentoo-user] Why IDEPEND's context is BHOST?

[Ionen Wolkens]

[-- 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 --]

[gentoo-user] [gentoo-ser] Re: Why IDEPEND's context is BHOST?

[Alexander Kurakin]

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]


Thanks, Ionen!
 
> then amd64 will need deps to run pkg_postinst
 
 
Why? Why does build participate on installation?
 
Is «cross emerge» cross building?
 
Sincerely,
Alexander Kurakin.
 
 

[-- Attachment #2: Type: text/html, Size: 486 bytes --]

Re: [gentoo-user] [gentoo-ser] Re: Why IDEPEND's context is BHOST?

[Ionen Wolkens]

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On Fri, Sep 02, 2022 at 11:03:21AM +0300, Alexander Kurakin wrote:
> 
> Thanks, Ionen!
>  
> > then amd64 will need deps to run pkg_postinst
>  
>  
> Why? Why does build participate on installation?

Maybe it's terminology confusion? CBUILD just means the machine from
which the package is being handled, not necessarily just "built".

Like amd64 builds the package, then installs it to
/usr/aarch64-pc-linux-gnu. That ROOT directory can either be used by
qemu, copied to a real aarch64 system, or used to make binpkgs.

> Is «cross emerge» cross building?

Yes, and it wouldn't work without any installation given e.g. need
to install cross libraries to link with it.

IDEPEND is fairly rarely needed anyhow, at most may have a eselect
module in there.

-- 
ionen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[gentoo-user] Re: Why IDEPEND's context is BHOST?

[Alexander Kurakin]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]


Oh, now I see.
 
CBUILD/CHOST are not (only) about "arch", it’s (also) about "phases" and "paths".
 
CHOST runs (already installed) packages’ binaries.
 
CBUILD does everything else: fetch sources, build sources, move built binaries (i.e. "install/merge").
 
Thanks!
 
P.S. If you can, reply, please, to  https://archives.gentoo.org/gentoo-user/message/cf1cbe72d7d2337f6ebf6a29c5460c3a
 
Sincerely,
Alexander Kurakin.
 
 

[-- Attachment #2: Type: text/html, Size: 856 bytes --]