cargo-update
cargo-ebuild
DISCONTINUED
Our great sponsors
cargo-update | cargo-ebuild | |
---|---|---|
11 | 6 | |
1,107 | 79 | |
- | - | |
6.6 | 0.9 | |
6 days ago | about 2 years ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-update
-
Rust 1.66
Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].
The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.
[0] https://github.com/killercup/cargo-edit
-
`cargo audit` can now scan compiled binaries
Would be nice if this worked with cargo-update somehow.
-
Hey Rustaceans! Got a question? Ask here! (26/2022)!
There is cargo install-update plugin: https://github.com/nabijaczleweli/cargo-update
-
go-global-update - the missing command for updating globally installed go executables
I didn't find any command or package to update those packages, and given that npm has npm -g update and cargo has cargo install-update, I decided to create go-global-update for go.
- cargo-update - A cargo subcommand for checking and applying updates to installed executables
-
I just realised Monday is now my favourite day of the week, because in my timezone it’s the day new rust-analyzer releases come out!
rust-analyzer isn't a rust component (like rust-src, etc. which will update with rustup update), nor a cargo binary (where you could use cargo install-update - https://github.com/nabijaczleweli/cargo-update ).
-
Git-cliff: generate changelog files from the Git history
I initially was interested in Rust because of performance + speed + safety, but now I have to say that cargo is a big selling point for me.
I always used to be scared of compiling software myself because I never seemed to be able to get it to work without endless headaches. Now, I generally find it easy to compile Rust programs if they aren't in my package manager, and with cargo install-update https://github.com/nabijaczleweli/cargo-update I find it easy to keep the software up to date. I have higher confidence that I can get hobbyist Rust software working, and the more Rust software I use, the more familiar I am with the ecosystem and the more comfortable I am.
If this was written in some obscure language I wasn't familiar with, I'd be less confident I would be able to run it at all, let alone keep it updated, and I may not bother even trying to install it.
-
DoorDash: Migrating From Python to Kotlin for Our Backend Services
So while it may take a while for some, it's already absolutely fine for me to compile my projects in a few seconds or a minute. I install all my related tooling via cargo install and update it via cargo install-update -a ( https://github.com/nabijaczleweli/cargo-update ) so I frequently/daily build different Rust projects and I'm quite ok with the compilation times.
cargo-ebuild
-
diziet | Debian’s approach to Rust
In Gentoo, Rust crates are just normal files to be downloaded in order to build a given package. The package pins (and checks the hashes of) the crate deps, and builds using cargo --offline. There is no serde/clap/etc packages, just ripgrep/librsvg/etc packages. There is no need to patch all packages to use the same serde crate version. Packaging a Rust program in gentoo is pretty much automatic.
-
How do I adjust fan curves on AMDGPU?
Then, I went through like 3 different pages on gentoo and learned how to make my own rebuild using this... But after setting up my custom repo and making sure it had the right permissions, manifest, etc. the ebuild failed on account of not being able to find the Config.yoml file it needed, which exists in the directory I built the ebuild from. I think I am just SOL on this, and will have to probably find a different approach
-
Cooperative Package Management for Python
FWIW it's worth for portage (Gentoo) there is g-sorcery[0], which can create ebuilds for Emacs (m/elpa) and python packages automatically. Similarly there is also cargo-ebuild[1] which can create ebuilds for rust programs/libraries, including a list of all dependencies with hashes.
I've successfully used cargo-ebuild in the past to create ebuilds automatically, it's a breeze. I'd be surprised if similar tools didn't exist for deb/rpm based distros.
-
Can Anybody Help Me With My Custom Ebuild for xplr?
I'm working on a custom repository where I intend to write ebuild files for packages that's not supported by Gentoo's repository. Right now, I'm trying to write an ebuild file for xplr, which is a Rust project that uses the Cargo build system. Initially, I used the cargo-ebuild tool, which generated the file xplr-0.14.3.ebuild.
What are some alternatives?
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Rustup - The Rust toolchain installer
cargo-bitbake - cargo extension that can generate BitBake recipes utilizing the classes from meta-rust
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
cargo-make - Rust task runner and build tool.
crate-deps
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
rustfmt - Format Rust code