mirror of
https://github.com/gentoo-mirror/gentoo.git
synced 2026-08-23 18:38:08 -07:00
3c265c179a
The way we access the shell-complete binary during the build has always been a hack. There is no way to know for sure where it is located ahead of time and cargo does not expose this information in an easily accessible manner. That may lead to shenanigans such as https://bugs.gentoo.org/889360, where it appears as if a debug build was forced and that resulted in the executable being available in target/debug/ as opposed to target/release/. Fix this issue by using cargo install internally, to force "temporary" installation in less undefined path. Closes: https://bugs.gentoo.org/889360 Signed-off-by: Daniel Müller <deso@posteo.net> Closes: https://github.com/gentoo/gentoo/pull/28938 Signed-off-by: Joonas Niilola <juippis@gentoo.org>