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
signature.asc
Description: PGP signature
