cargo ebuild --SCRATE

[necrose99]

cargo ebuild enhancment to git clone those really pesky SOB crates or if crate x is not in crates.io.

repoman DIE sourcing x,y but 99.5 % of crates sourced.

cargo ebuild --scrate git./bar....... --scrate url foo.git ....

git clone 2 crates that aint in crates.io or encase of know breakage under specific platforms...
git clone , >>> /work call down the crates , build done.. however such eclass sorcery might be (Gentoo Heresy at the moment)
ordo git to crate on the fly to shut up build system.
2 crates missing git clone > crate , git clone > crate done , building portage happy.
akin to EGO-sourcing in golang. as needed.

yank and bake .. do crates , cargo update toml 9999 ebuild equiv ...
might be related to workspace issues. ...

https://github.com/RustPython/RustPython not only a systems python but WASM ... lovely
gives cargo-ebuild Indigestion at times too.

starship shure it'll build fine under amd64 , however under Saki's Gentoo build for rpi4 repoman dies on the crates,
starship/starship#1431

artichoke
cannoli RUST PYTHON subset ie porthole gentoo killed might have ben able to perma freeze as a rust crate. ,

all pulls in rust overlay,..

[necrose99]

https://github.com/williamh/get-ego-vendor
pentoo-overlay has simular toml to ego bits.. via shell script yanks urls to go's much like crates, in crago-ebuild

however the golang esclasses can also yank foo-bar go project down with ego-vendors.. tar-ball/git ...

wondering if you have a few PIA crates , you could Just "s-crate" or VENDOR them in golang AKIN terms..

forgive my tangent , for lack of a better analogy for rust to fix those peskier crates...
builds by hand but not by cargo-ebuild ...