Support install directly from git repo

[cargo-bins]

Support install directly from git repo

[passcod]

I think with git there's a way in the protocol to only fetch particular files or at least subtrees, which would make it a lot more efficient than cloning the repo, but a shallow clone is a good start.

[NobodyXu]

@ryankurte @somehowchris @mpizenberg cargo-binstall v1.0.0 has released, which support this feature!

[passcod]

Yeah so this would be the same as cargo install --git https://..... Conceptually it would shallow-clone the repo then run as if it was invoked with --manifest-path cloned-repo, plus it would read the manifest and pick the crate name + version out of it if that's not provided on the command line.

[somehowchris]

I've seen that gitoxide would be an alternative to git2, @passcod you seem to have an eye on that project for some other things, would it be an option for something like this?

Would this only be for unpublished crates? Or in general something to get metadata from a git repository. i.e. for use at companies with a host such as gh enterprise, bitbucket,... and a binary host such as artifactory? Not that I propose a lock in for host cases but just the general purpose

[NobodyXu]

Would this only be for unpublished crates? Or in general something to get metadata from a git repository. i.e. for use at companies with a host such as gh enterprise, bitbucket,... and a binary host such as artifactory? Not that I propose a lock in for host cases but just the general purpose

I'm also a little confused about this.

For unpublished crates, one piece of information we need is Cargo.toml, src/main.rs (if present) and anything under src/bins/ if present.

We don't actually care the content of src/main.rs or src/bins/*, but we need these vfs information in order to infer the list of binaries to install.

[mpizenberg]

Also interested in this as I'd like to avoid pushing my binary crate to crates.io.