-
Notifications
You must be signed in to change notification settings - Fork 13
cargo ebuild --git #44
Comments
I don’t understand the ask here. Can you clarify? |
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 , D: add git or option to tarball ... unpack vendor tarball to the ./work/crate path... 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" 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) |
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..
The text was updated successfully, but these errors were encountered: