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
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmMQyykACgkQskQGsLCs QzT+Agf9EZxGgy+BfcYyl/nXoYr97V5P89QLKVMov7+C4ZA79kfI9A+cLdWNMBKz HMRBUsbG+DVk8i0lW3+G6sXS/uwA6D9zKo1Z97bdTz45oP26qRqeNiXOFqzPf5Ze 3UTWPa2/viHLQTrZ1EbHfCw32kzeV3Bqj7YEdaQSadP37Zg/NhTPIj0IIpBOybzj 4KDGnBkDXWuhlN//w6vPwV37iP/6OExYR61jTigjFZ5hdd6YRgLx7vysZv/9eqc/ teLgzrThzCbV3y2Y6QIJYV9XeQu6k23BT9yG8n1Q9eWi/dUXG8c3h1hD46f8PN0x T2ONGEyRwMc+sUZ4eYRSOSITDxgy6w==
=4GN4
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)