cargo-msrv
paru
cargo-msrv | paru | |
---|---|---|
11 | 74 | |
752 | 5,505 | |
- | - | |
9.1 | 8.8 | |
8 days ago | 5 days ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 only |
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-msrv
-
Introducing cargo-ft: a cargo extension for specifying supported targets for a crate
What this tool say? https://github.com/foresterre/cargo-msrv
-
What’s everyone working on this week (19/2023)?
I'm working on cargo-marv.
-
What's your crate's Minimum Supported Rust Version?
Before getting overcome by despair, have a look at cargo-msrv -- this little gem of a tool figures it all out for you!
-
What's everyone working on this week (31/2022)?
I'll be adding a 'minimal' output format to cargo-msrv for use in scripts. I'll also be updating the book, and inch closer towards releasing v0.16.
-
Rust for the Kernel Could Possibly Be Merged for Linux 5.20
First commit 2 months ago, started with edition 2021. https://hg.sr.ht/~cyplo/legdur/browse/Cargo.toml?rev=ca11815...
Have you tried compiling something less than bleeding edge, with a year old compiler, or are you picking projects specifically to "showcase" the supposed failings of the Rust compiler?
Many libraries in the ecosystem have a MSRV (minimum support rust version) guarantee, with compile-time shims to enable newer features if a more recent version is detected.
You can pin your dependencies to those versions (and if they don't have an explicit MSRV, just pin it to a version by date or by running https://github.com/foresterre/cargo-msrv on the project to find the effective MSRV).
You can cargo install specific versions of a binary crate, and if they move to the 2021 edition, or use a recently stabilized standard library function or w/e, you can simply choose to install a specific version, that would work with your distro's rustc/cargo.
I'm not even talking about the completely valid, but last resort strategy of many non-bleeding edge distro package maintainers, of simply creating a .patch file and applying it. In legdur's case, --- edition = "2021" +++ edition = "2018" on Cargo.toml would probably do the trick. For libraries/binaries you control, you can use https://doc.rust-lang.org/cargo/reference/overriding-depende... and https://github.com/itmettkeDE/cargo-patch.
Giving up after the first minor roadblock and crying bloody murder is intellectually lazy.
-
[Gitoxide in January]: full multi-index support in object database and complete git-index reading
Looks helpful though it doesn't seem to address when you don't have a Cargo.lock. I've created an issue for this.
-
What’s everyone working on this week (8/2022)?
I'll be switching over the CLI of cargo-msrv, from Clap's builder methods to the attribute macro. I hope this will simplify the configuration, as my Config and ConfigBuilder structs (which were build from Clap's ArgMatches) was growing fast, and becoming slightly unorganized. With the attribute macro, the config will be constructed directly by code generated by the macro. The mostly saves one intermediate step, and a lot of boilerplate.
- cargo-msrv v0.14.0 release
-
Announcing `cargo supply-chain`: Know whom you trust
Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.
paru
- Release Paru v2.0.0 (AUR helper)
-
what do you wish you knew while starting to use arch?
I would also get a AUR helper, I'd recommend paru (don't forget to configure /etc/paru.conf). Just make sure you're checking the validity of AUR packages.
-
Paru not upgrading *-git packages
as the uncommented lines. This has been the default since at least April 2022.
-
Is anyone editing PKGBUILD files locally with paru (local changes without "customizepkg")?
I've just discovered that paru supports adding your own changes to PKGBUILD files if they are committed to the cached git repos and merging them with any upstream upgrades:
-
Discovery gives "The PackageKit daemon has crashed" error suddenly (Arch)
If you use AUR packages, you might want to use an AUR helper that wraps pacman, like paru or yay.
-
Concerns Over Arch Stability
paru is an AUR Helper, which also will perform pacman actions (install, upgrade, removal, etc)
-
It’s JavaScript all the way down
maybe check out paru - it throws up the PKGBUILD whenever you’re installing a package (or upgrading one when it’s changed)
-
Is there any software helps build AUR packages and update them?
paru: https://github.com/Morganamilo/paru
-
Need help installing webcam drivers ipu6
Thanks. Installing intel-ipu6-dkms-git from AUR using paru is giving error, says
- Is there a way to apply a patch to an AUR package on the fly, without editing the PKGBUILD?
What are some alternatives?
toml-bombadil - A dotfile manager with templating
yay - Yet another Yogurt - An AUR Helper written in Go
crates.io-index - Registry index for crates.io
octopi - A powerful Pacman (Package Manager) front end using Qt libs
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
aur - A secure, multilingual package manager for Arch Linux and the AUR.
rust_lisp - A Rust-embeddable Lisp, with support for interop with native Rust functions
rua - Build tool for Arch Linux providing control, review and jailed build options
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).
ArchWSL - ArchLinux based WSL Distribution. Supports multiple install.
competitive-programming-rs - Algorithm Snippets for Competitive Programming in Rust
topgrade - Upgrade everything