cargo ebuild --git

[necrose99]

cargo install --git known....

a few packages the authors are miffed by copycats on namespaces , are or ppl will poison the version update well..

cargo ebuild --git , IE add cargo vendor git-r3 9999 etc's to ebuild and git clone to rust crates / {misc auto-magically stuffs} crates.io for more public.. crates..

other than that sub packages in project/root/sub-crate could use bits of love..

[cardoe]

I don’t understand the ask here. Can you clarify?

[necrose99]

if [[ ${PV} == *9999 ]]; then
    **inherit git-r3**
    EGIT_REPO_URI="https://git.kernel.org/pub/scm/git/git.git"
else tag....  EGIT_COMMIT 
 cargo-ebuild --tag= hash...... 

EGIT_CHECKOUT_DIR = to unpacked work crate/s to build..

else SRC_URI ="{($cratesURI} " to tarball .. cratesURI=all the pubic crates..

A: " I'm not going to publish they to crates.io anymore, it's a problem when you have to add your own crate fork to dependencies and then you aren't able to publish anymore there. Happened with Findomain and I had to yank more than 30 releases." unimap author

B: some authors are stung at keeping crates up at crates.io .... | this can make packing some rust tools for weekend warriors /novices more irksome...

C: cargo ebuild also won't seem to drill into Main-crate nest of crates if it needs to build sub-modules.. included in src packages.

cargo install --git https://github.com/Veil-Project/Veil-Rust will build subs , unfortunately each sub is a cargo-ebuild pass.. cargo ebuild tends to not like nested things.. ie sub modules..

D: add git or option to tarball ... unpack vendor tarball to the ./work/crate path...
`cargo ebuild --git=https://github.com/cardoe/cargo-ebuild.git ebuild.git" --hash=b67e6cb268e49bc959285f39a70c8947e36b8f70 ---inset into ebuild --- along with some automagical inherit git-r3 EGIT_REPO_URI="https://github.com/cardoe/cargo-ebuild --9999 [--pass=cargo-update] generate a 9999 , cargo update @ live ebuild... from updated toml

EGIT_COMMIT ="b67e6cb268e49bc959285f39a70c8947e36b8f70"`

aka https://github.com/cardoe/cargo-ebuild/releases/tag/v0.3.1

ie git clone vendor produces 98% ebuild , but the last mile so to speak of is feeding the tarball or git to fetch the src.. and not having a busted ebuild

E: adding some cli switches to generate ebuild on fly to go Get the damn tarball and or git repo " more automagically" Useful for more novice/mere mortals of users.. and or scriptable for version bumps... on authors more stubborn on CRATING their rust/s

F: crate= foo {$work/bar/src/foo/src} for crate foo cli option to aim at in src tree relative path crate/s also a nice to have refinement.. ie build crate etc , then build main items... --insrc-crate="$relativepath"

G: --pass=cargo-update (other src-prep->cargo-ebuild or qa etc fixes)