cargo-binstall | Binary installation for rust projects
kandi X-RAY | cargo-binstall Summary
kandi X-RAY | cargo-binstall Summary
cargo-binstall is a Rust library. cargo-binstall has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
Binary installation for rust projects
Binary installation for rust projects
Support
Quality
Security
License
Reuse
Support
cargo-binstall has a low active ecosystem.
It has 147 star(s) with 7 fork(s). There are 3 watchers for this library.
It had no major release in the last 12 months.
There are 14 open issues and 8 have been closed. On average issues are closed in 16 days. There are 6 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of cargo-binstall is v0.6.2
Quality
cargo-binstall has 0 bugs and 0 code smells.
Security
cargo-binstall has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
cargo-binstall code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
cargo-binstall is licensed under the GPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
cargo-binstall releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cargo-binstall
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cargo-binstall
cargo-binstall Key Features
No Key Features are available at this moment for cargo-binstall.
cargo-binstall Examples and Code Snippets
No Code Snippets are available at this moment for cargo-binstall.
Community Discussions
No Community Discussions are available at this moment for cargo-binstall.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cargo-binstall
binstall works with existing CI-built binary outputs, with configuration via [package.metadata.binstall] keys in the relevant crate manifest. When configuring binstall you can test against a local manifest with --manifest-path=PATH argument to use the crate and manifest at the provided PATH, skipping crate discovery and download.
pkg-url specifies the package download URL for a given target/version, templated
bin-dir specifies the binary path within the package, templated (with an .exe suffix on windows)
pkg-fmt overrides the package format for download/extraction (defaults to: tgz)
name is the name of the crate / package
version is the crate version (per --version and the crate manifest)
repo is the repository linked in Cargo.toml
bin is the name of a specific binary, inferred from the crate configuration
target is the rust target name (defaults to your architecture, but can be overridden using the --target command line option if required()
archive-format is the filename extension of the package archive format
binary-ext is the string .exe if the target is for Windows, or the empty string otherwise
format is a soft-deprecated alias for archive-format in pkg-url, and for binary-ext in bin-dir; in the future this may warn at install time.
pkg-url specifies the package download URL for a given target/version, templated
bin-dir specifies the binary path within the package, templated (with an .exe suffix on windows)
pkg-fmt overrides the package format for download/extraction (defaults to: tgz)
name is the name of the crate / package
version is the crate version (per --version and the crate manifest)
repo is the repository linked in Cargo.toml
bin is the name of a specific binary, inferred from the crate configuration
target is the rust target name (defaults to your architecture, but can be overridden using the --target command line option if required()
archive-format is the filename extension of the package archive format
binary-ext is the string .exe if the target is for Windows, or the empty string otherwise
format is a soft-deprecated alias for archive-format in pkg-url, and for binary-ext in bin-dir; in the future this may warn at install time.
Support
binstall works with existing CI-built binary outputs, with configuration via [package.metadata.binstall] keys in the relevant crate manifest. When configuring binstall you can test against a local manifest with --manifest-path=PATH argument to use the crate and manifest at the provided PATH, skipping crate discovery and download.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page