Re: [PATCH 1/2] cargo.eclass: for EAPI 9, ban cargo_src_install

Michał Górny <[email protected]> Fri, 29 May 2026 12:33:10 +0200
Newsgroups gmane.linux.gentoo.devel
Organization Gentoo
Message-ID <[email protected]>
On Thu, 2026-05-28 at 17:56 -0400, Eli Schwartz wrote:
> This was always a terrible idea. cargo pretends to be a package manager
> and a build system, but is neither -- only a compiler-wrapper.
> 
> "cargo install" recompiles the binary so it is not what you tested in
> src_test. It does so during the src_install phase, and it (mostly?)
> doesn't respect incremental builds or caching intermediate outputs. It
> also cannot install anything other than what doexe does, since cargo
> doesn't support *building* multiple output types, let alone installing
> them in a uniform way.
> 
> Simply require users to use doexe like for any other package without a
> standard (autotools, meson, cmake etc.) build system.
> 

Sorry for asking the hard question, but is there a reason we can't do it
like with Python -- just execute 'install' immediately in compile phase?
Having to reinvent the wheel is kinda annoying.

-- 
Best regards,
Michał Górny
signature.asc (application/pgp-signature, 293 B)
-----BEGIN PGP SIGNATURE-----

iKQEABYKAEwWIQQcFD0bEK7NPNmWHtiOMjR69AVa6AUCahlrZhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDISHG1nb3JueUBnZW50b28ub3JnAAoJEI4yNHr0BVro
p2YBAKdYripiHrES+o0ZOEND+RcSItWRfA+urtikCVTt2cCAAP9WFNPNGWSz3TaZ
DzWU26k6sQTiLzZrOi0bBC++RrbwBQ==
=vitw
-----END PGP SIGNATURE-----